How (My) Stardates Work

It’s only fair to point out that there is no “real” system for stardates. In fact there were quite deliberate attempts to ensure that there was no rational system to stardates at all, just so that no-one could accuse the show of getting things wrong. My suggestions here are just suggestions, and no more. They require an awful lot of “tweaking,” selective interpretation of the evidence and a charitable disposition on the part of the reader. In the end, I stuck with stardates, mainly because it seemed really strange not to use the chronological system used in the show in a chronology.

For people who like long explanations, I have written a much longer introduction. This is just a quick “how to.”

Alas, nifty Java calculators are quite beyond me, but if you want to play around with stardates (and other dates, too), there’s a spreadsheet on the Calendars page.

Stardates, as I See Them

The base unit of the stardate is 78,500 seconds long.
The time between S.D. 41XXX and 42XXX is 400 units, or 363.426 days.
How can that be, since there are stardates clearly implying that there are 1,000 stardates in that period, counting sequentially? My way of getting around this particular hurdle is that every stardate has a “time-space correction factor” added to it. For my purposes, that takes the form of a random number between 0 and 6, multiplied by 10. Although it isn’t immediately self-evident, there are a few occasions where it is quite plain that when it is S.D. 44723.4 in one part of the Federation, it’s S.D. 44703.4 somewhere else. How else can the launch of the São Paulo be on S.D. 52889.3, and yet it’s S.D. 52861.3 when Captain Sisko takes command?
As you can easily guess, these “time zones” aren’t terribly straightforward. The “time-space correction factor” doesn’t remain constant, even when you’re considering a single location in space, such as Deep Space 9. I’ve assumed that the whole thing is part of that currently unknown branch of physics that supports warp drive, subspace radio and transporter beams and not gone into it too deeply. The number is obviously recalculated often, and operates in a more complicated way than you might expect. As an example, it would be reasonable to expect that S.D. 51999 would be followed by S.D. 52060, given a “time-space correction factor” of 60, and yet the available evidence is that it’s most likely to be S.D. 52000 that comes next, implying that the system zeroes if it hits the maximum possible value, and all the calculations start again. Naturally, stardates become even less easily comprehensible for moving objects, like starships.

This is Really It?

I’m afraid so. It's based directly on the on-screen evidence, and I haven’t come up with anything else that works even a fraction as well. Every official explanation of stardates ever published is very clear that they reflect location as well as time, so how else is that requirement to be addressed? “Star Trek” is, after all, a science fiction story: not everything can be explained in full detail, and sometimes you just have to accept things.

The ultimate starting point for my stardating system is 00:00:00 on Wednesday 25th February, 2224; J.D. 2533413.5: S.D. (0)00a0.0. Stardates then count upwards from there, right through into the “five digit” stardates of the 24th century. All of the stardates in the chronology have been calculated according to this system, which is why there is a number in brackets at the start of them. Since the stardates count up in a regular way, it’s possible to set things up so that the first digit of the stardate is always omitted, placing the shift from “four digit” to “five digit” stardates at the point where S.D. 1000a0 is reached; Monday 27th August, 2323 in my system.

This does raise the question of why something as useful as a leading number to keep stardates straight never gets used, except in one (very dubious) case? My theory is that the leading digit is a “later addition” that wasn’t part of the original system. If stardates were intended as a temporary expedient, then they could just “roll over” until they were replaced. After a certain length of time, it would make sense to distinguish between the various “cycles.” It’s quite possible that my “ultimate zero date” might be nothing of the kind, that stardates were introduced at an earlier or later point, and the “longer” stardates set the notional S.D. 1000a0 point. It might even be that stardates are primarily a military dating system, and it’s “traditional” to omit the first number.

All I can say for certain is that the “extra” part of the stardate is omitted, and I think that’s probably because it wasn’t part of the original data. It is extremely useful (rather like the “reference stardates” in the FASA roleplaying game) so I’ve included it in my dates.

Any given stardate will have between one and four possible “normal date” values. For example, S.D. 44392 has to be Tuesday 24th October 2367, because the “space location correction factor” has to be at its maximum value of 60, whereas S.D. 44372 could be Friday 6th, Sunday 15th or Tuesday 24th October, depending on the “time-space correction factor.” This is a vital flexibility for me, and I have to assume that the people “really” using stardates in “Star Trek” find the system useful and informative about things I just can’t guess at. Of course, since my stardate units don’t match exactly with days, all of these date conversions could stretch over into adjacent days. I’ve picked the date at 44392.5 and 44372.5; all this is complicated enough already.

How Do People Measure the Time on Starships?

Initially, I assumed that stardates were the standard way of keeping time aboard ship. After all, when the fake Lincoln asks “Do you still measure time in minutes?” in TOS “The Savage Curtain”, Captain Kirk replies “We can convert to it, sir.” (Thanks as usual to Chrissie’s Transcripts website for this quote.) That was one of the reasons I became so attached to the idea of a stardate unit being a 24-hour day. Whilst there is some argument for adopting a “stardate day” for use on starships, mainly to get more of the “stardate fractions” to work better, I think the evidence is overwhelming. Deep Space 9 keeps Bajoran time, and Starfleet ships keep Earth time. Why? Because people know what day of the week it is, when festivals will fall, even what the year is (although all these things are subject to weird lapses). They also use the standard 24-hour clock to measure the time.

It might be possible to “tweak” the relationship between the UTC time and stardates to get things to work slightly better. My own feeling is that every “solution” will just raise a different crop of problems, so it’s better to keep things simple. Of course, I reserve the right to change my mind.

This also addresses a question that I’d kind of dismissed before; isn’t is awfully confusing if the date keeps flipping around? Potentially, you could get up on S.D. 45213, eat breakfast on S.D. 45203, report for duty at S.D. 45233. You can see the problem. Although the stardates as used don’t seem quite that volatile (except “off-screen”) there’s nothing in what I’m suggesting to rule that out. If the stardate is simply used to fix things like log entries and space phenomena to particular time, then this problem is going to be much less pronounced.

Since When is It Up to You to Change Stardates?

Put simply: it isn’t. Some stardates can be made to agree with my ideas, some just can’t. All of the stardates quoted in the timeline reflect the actual dates used. Sometimes they agree with the place I’ve put them, often they don’t.

Introduction to Stardates

by StrauchiusStrauchius on 05 Dec 2010 21:08, last updated on 09 Mar 2016 14:33