You are using a browser which is not compatible with CSS (for more information, see Tara's tutorial).
Because of this, it is possible that our website may not appear
correctly in your browser. We apologise for the inconvenience, and
recommend you upgrade your browser to one which is compatible with CSS.
For more information, please visit our Browser Upgrade page.
thank you for that. I found it with google and i really enjoyed it.
Best regards
Michael
Now If I can only figure out the time difference between GMT and the US time after we switched to earlier summer time !
Regards,
scriptster
http://www.1-script.com
9999999999 translates to Sunday, September 7th 2014, 4:50:07 (GMT)
Great tool
btw
1234567890 translates to Friday, February 13th 2009, 23:31:30 (GMT)
got to be the end of the world hasn't it?
in Case, if anybody wants code / formula in C#..
DateTime origin = new DateTime(1970, 1, 1, 0, 0, 0, 0);
TimeSpan diff = DateTime.Now - origin;
string strTime = Convert.ToString(Math.Floor(diff.TotalSeconds));
1193152432325
Also you might want to add daylight saving.
http://www.sc2talk.com
Try it out. It seems that GMT +<anything> wraps to 1901. I wonder if unix systems which still use the 32-bit signed int have this problem when displaying time for this value?
http://www.digajax.com
The Timezone-Dropdown could be more comfortable with cookies, I guess, but anyway, it's quite nice as it is atm.
http://www.csto2.de
Came in handy today
weird...
thanks for this fun time-waster
Hi
Where is code?????????????
Try it out. It seems that GMT +<anything> wraps to 1901. I wonder if unix systems which still use the 32-bit signed int have this problem when displaying time for this value?
Example?
Serverlocation -> Switzerland
We have GMT+1
If we give now the timestamp: 1176933600
in this tool, what we get?
Exactly: Wednesday, April 18th 2007, 23:00:00 (GMT +1)
...hmmmmmmmmmmmmmmmmmm, I tell you a secret... every Apache Server will tell you that 1176933600 is actually the 19th April 2007 at 00:00:00
This script forgets that Middle Europe has in the summertime 2 hours difference to GMT.
Be careful with it, better use the timestamp converter on this site: http://www.01-scripts.de/timestamp.php ...or check the dates yourself in php to be 100% sure.
++Bookmark
W.>
thanx man
TY
useful &
handy.
Many many thanks
Looking at a world timzone map and understanding the rotation of Earth and when the sun comes up on each timezone may help you understand.
GMT - 8 means that you have to subtract 8 hours from the time in GMT - 8 to get the actual GMT time.
GMT + 8 means that you have to add 8 hours from the time in GMT + 8 to get the actual GMT time.
GMT - 8 is actually 8 hours ahead of GMT and GMT + 8 is actually 8 hours behind GMT.
GMT - 8 is to the east of GMT, so when it is 1AM in GMT it will be 9AM in GMT -8. 9AM will give a larger timestamp than 1AM.
GMT + 8 is to the west of GMT, so when it is 1AM in GMT it will be 7PM on the previous day in GMT +8, giving a smaller timestamp.
Let's say we want to convert 5:00PM GMT +8 and 5:00PM GMT -8. When it is 5:00PM at GMT +8, it will be a certain timestamp.. (eg. 26467365) It will take another 16 hours before it becomes 5:00PM in GMT-8. And that is why the timestamp for 5:00PM GMT -8 is larger than 5:00PM GMT +8.
--------Start Quote----------
Beatnik, thanks for the reply. I apologize if I missed your point, but seems like my question remains: how could GMT -8 produces a larger timestamp than GMT +8 for the same date? GMT +8 is supposed to be 16 hours ahead of GMT -8, therefore has larger timestamp...no?
Thanks!
--------End Quote----------
strtotime("10 September 2000")
etc... so having only the unix number will i be able to retrive correct date and number of days?
Great tool i too use it everyday for my unix script and SQls ... Thankx whoever created this tool..
Other than that, great work and keep it up!
A small suggestion for the top form...the time zone selector goes back to the default every time you load the page. I think it would be better if it stayed on the time zone the user selects...I hope that makes sense.
Many thanks for informing me of this. There was a small problem with the code which loads the comments, which meant that a single query (which looks up the words which should be censored) was being run for every comment, instead of being run only once. This has now been corrected.
Well done
But was toot diffcult to find ;o)
Thanks for this tool.
Bye,
Basty
That makes sense now. Unix timestamp is taken at GMT (UTC), so you gotta convert everything to GMT first, then count the seconds since January 1, 1970.
You are quite clear, just have to read it couple times
Thanks again!
Watch the outputs that are given.
All the clues are there.
I enter Sunday, January 1st 2006, 0:00:00 for both my tests. Note the time is midnight.
Results:
Sunday, January 1st 2006, 0:00:00 (GMT) translates to 1136073600
Sunday, January 1st 2006, 8:00:00 (GMT -
Note how, although I had not altered the time from 0:00:00, it changed the time to 8:00:00 on my second test.
This shows why you have a greater number when you go back. All timestamps are GMT:
Midnight in GMT means it is 4pm in (where-ever GMT-8 is). However, when it is midnight (where-ever GMT-8 is), it is actually 8am in GMT.
Thus midnight on the -ve side of GMT will have a greater timestamp with this tool, and those on the +ve side of GMT will have a lesser timestamp.
Or did I just confuse everyone more ?
Nice little Tool
Currently it silently converts to a signed value and misguides anyone using it.
Quote:
Let's review what Beatnik said:
Quote:
The timestamp is constant through all timezones. It is the timezone offset (eg GMT-6) that give your time in your locale.
If you are doing server work - your server will hold the GMT timestamp, and will convert when READING the timestamp, to your servers timezone offset. Always store in GMT.
What he is saying is that timestamps are always stored in GMT. This means that when you create a timestamp from a date, first you have to convert that date/time to the time it was at that instant in Greenwich, and then get the number of seconds from that. So, for example.. if we have the date January 1, 2006, at 1:01:01 in the western united states (GMT -7 timezone, which is west of greenwich).... at that exact instant, it was Sunday, January 1st 2006, 8:01:01 in Greenwich. ... this produces the timestamp 1136102461.
Doing the same thing (using the same starting date/time) only with a different timezone (GMT +7, which is EAST of Greenwich), .... at that exact instant, it was Saturday, December 31st 2005, 18:01:01 in Greenwich.... Then we convert that to a timestamp, and we get 1136052061.
What this means (using more general terms) is that you can think of timestamps as being absolute instances in time, regardless of timezone. So if you compare the instance in time when it was Jan 01, 2006 01:01:01 at a place east of greenwich to the instance in time when it was Jan 01, 2006 01:01:01 at a place west of greenwich.... obviously, the place in the east reached that date/time first (using an absolute point of view)... and the timestamp will reflect that. ....
The seemingly contradictory results happen because the input date is relative, and the timestamp is absolute. In other words, it was the new year first in the east (smaller timestamp), and then it was the new year in the west (larger timestamp). (The east was in the new year before the west).... and the timestamps reflect that.
Hope this helps
Thanks!
Don't know if anyone commented on the first comment. (or is it the last? - the top one on the page as I'm viewing!).
This page includes timezone.
If you are using this page to get a straight conversion, you should remember that the true timestamp must be set at GMT.
The timestamp is constant through all timezones. It is the timezone offset (eg GMT-6) that give your time in your locale.
If you are doing server work - your server will hold the GMT timestamp, and will convert when READING the timestamp, to your servers timezone offset. Always store in GMT.
Thanks
regards,
Brian
www.linc.com.mx
props to the maker
Had to make a few adjustments to my site www.kaltersiashqiptare.com and it helped a lot.
thank you
I used this tool to calculate the exact date and time, that my father (for the only time in our lives) are exactly twice as old as me!!!
That's when you reach the age your father had when you was born
anyway-- i want to build an array which will give me a certain amount of hour options for an event time in my dropdown list. it looks like your little converter thing here has just the code that i need inside (well... hmm... maybe not), so i thought if i could get a look at the script, i could probably skim what i need to make my array-- or if any of y'all have an idea for me, i'd be all happy inside.
thank you!
http://www.snapfiles.com/download/dlunixtimestamp.html
http://www.interdoc.ch/mouvement-danse
converts a date in cel A1 to the strftime time stamp
and the conversion from strftime time stamp to excel time stamp
Banging my head against the wall perhaps.
If it can have the NOW timestamp without the need for me to push that button (to have the timestamp when i acces the page) it will be perfect
thanks
2222222222 gives me 26.04.1904 21:28:46, and 26.04.1904 21:28:46 gives me 2072745074, which gives me September 7th 2035, 2:31:14... so what the hell is this tool doing??? giving some random long-integers out? *g*
Is it possible for me to use this tool, even though the unixtime is unsigned? my unix time is "-279491583, and this should give me a result around this week. but it gives me 1978
can someone help me?
best regard
roald
Tşk. - Thx
Thanks to google and you, you made my day
I know it loads the current time on first logon - but not on page refresh.
Thanks in advance.
It helped me to much...!!!
Good Job!
28
03
2004
01
00
00
GMT
the result is:
Thursday, January 1st 1970, 0:59:59 (GMT) translates to 3599
I think this is a good script as-is, as noone can make scripts for you, unless they are making an entire CMS for you.
It's very simple, but it may help some beginners..
I'm currently making a bit more advanced project, with php/mysql, where I have one table with every country in the world and one table with timezones.
I then run queries to get the two-digit country-name (US, UK, NO, DK, etc.).
If I find more than one row (like mexico has), I let the user select his timezone..
If there is only one row (like Norway (NO)), I just select that as default and insert into the users table.
it's still in development.. my project uses the putenv("TZ=...
1057014000 in GMT +1 corresponds to 1057010400 in GMT. What the script does is take the date/time you enter, convert it to GMT (in this case move it back an hour), and convert the result which is in GMT to a Unix timestamp. The timestamp which you are claiming is "right" is not a GMT timestamp, but a GMT +1 timestamp.
It's not really a bug - I know that's what happens. Unless this is a real problem for anyone, I won't be changing the way it works.
its returning -1
it´s worth a bookmark and to tell friends
Great tool!
But it will be nice if i can choose the timezone.
David, Austria
can anyone help?
From what I've been able to find, the three extra digits are due to the timestamp being in microseconds, as opposed to seconds. However I don't see why it should cause a problem to remove the last three digits...
can anyone help?
A thoroughly usefull tool. Saved me writing one.
Straight into my book marks.
Quote:
It'd be cool if it put the current values in it instead of "0" if i don't enter anything.
thx!
greetz of switzerland
in bookmarks too =)
can you send me the source code for the Date to Timestamp program ???
Regards,
Andres
Add a new comment