This is the part of online D&D that ruins the most campaigns and gets the least attention. A modern online D&D table seats players from multiple continents as a matter of routine, and "Tuesday at 7pm" means seven different things depending on who's reading it.

If you're trying to run a weekly session across US, UK, and EU players, you've already learned the hard way that the wrong slot kills the campaign before session three. This piece is the math, the three real postures most online tables fall into, the daylight saving traps that move your goalposts four times a year, and the rule that holds a transatlantic table together. Guildhall's Timetable is being built to handle this conversion at the platform level; until that's live, the math below is what you need.

For the broader online-D&D guide (VTTs, voice, sync vs async, scheduling tools), see Play D&D Online in 2026. For the community side (finding a group at all), see How to Find a D&D Group Online.

The Three Time-Zone Postures

Most online tables in 2026 fall into one of three configurations. Each has its own slot math.

Posture 1: US-only table (coast-to-coast)

The US spans six time zones if you count Alaska and Hawaii. A US-only table can easily seat HI, AK, PT, MT, CT, ET, and AT players, and the spread changes what a single timeslot means.

A campaign that meets at 9pm Eastern is:

A coast-to-coast US table is roughly the same difficulty as a UK + EU table: a six-hour spread, but only one major DST split (Arizona and Hawaii do not observe DST).

Posture 2: UK + Europe table

A UK-anchored table that meets at 8pm BST (British Summer Time) lands as:

A UK + EU table is the simplest cross-border configuration in 2026. The spread is only two to three hours; the slot holds across the working week without anyone playing past midnight.

Posture 3: Transatlantic table (US + UK + EU)

This is the configuration that tries the hardest. A transatlantic campaign at 8pm BST is:

The same transatlantic table at 8pm ET is:

The hard truth: a weeknight transatlantic table is almost always a weekend table in disguise. Saturday afternoon in the UK + Saturday morning in the US is the slot most transatlantic tables converge on. Saturday 5pm BST / 6pm CEST / 12pm ET / 9am PT sits inside the daytime hours for everyone, every week.

Five Practical Rules from Cross-Border Tables

1. Anchor the schedule in the time zone where most players live, not where the GM lives. A London GM running for four East Coast US players who insist on a 7pm BST start time is asking the four players to play at 2pm Eastern on a Tuesday. The table will lose them by session four.
2. Saturday is the transatlantic default. Weekend afternoons collapse the gap. Weeknights almost always don't. If your transatlantic table is on a weeknight, expect attrition before session six.
3. Daylight saving time will move the goalposts up to four times a year on transatlantic tables. US DST starts the second Sunday of March and ends the first Sunday of November. UK BST starts the last Sunday of March and ends the last Sunday of October. Central European Summer Time follows the UK pattern. The two-week gaps in March and October are real and shift the relative clock by an hour for that window.
4. Hawaii and most of Arizona don't observe DST. Iceland (Reykjavik) doesn't either. A table that includes any of those plus a DST-observing zone will see a relative shift on the changeover dates regardless of how you anchor.
5. Write both endpoints into every listing. A clean format is "Saturday 8pm BST / 3pm ET, weekly, holds across DST." Both endpoints stated. No conversion math left to the applicant. Half the listings on r/lfg and r/UK_TTRPG fail this; the half that pass tend to be tables that last.

The Daylight Saving Trap (And How to Beat It)

There are eight DST changeover events relevant to a US + UK + EU table in a calendar year:

Two windows a year where the transatlantic gap is one hour off the rest of the year. A table that scheduled "Saturday 8pm BST / 3pm ET" for nine months may suddenly find itself meeting at "Saturday 8pm BST / 2pm ET" or "Saturday 8pm BST / 4pm ET" for two weeks in March or October.

The fix is to say so in the listing. "Saturday 8pm UK time, US players adjust by your local DST" is honest. "Saturday 3pm ET" without the UK anchor is a hidden trap. The Timetable is being built to resolve all of this at the platform level: each viewer sees the slot in their own local time, with DST changes computed automatically, so the listing is true in March and true in October without the GM having to update it.

The Listing Anchor (Both Endpoints, Always)

Most cross-border listings on r/lfg, r/UK_TTRPG, and r/dndberlin fail one of three checks. Compare a strong listing against a weak one:

Weak: "Wednesday 7pm, 5e, looking for two more players."

Time zone unstated. Implicit local-to-the-poster. A US poster means 7pm ET. A UK poster means 7pm BST. Five hours of ambiguity that gets resolved only after someone applies and asks. Most applicants don't ask; they apply, find out, and ghost.

Stronger: "Wednesday 7pm BST (2pm ET), 5e, looking for two more players, US East Coast and UK welcome."

Both endpoints stated. Audience scoped (no Pacific Time players will apply expecting to play at 11am local). Time zone math done for the reader. Half the work of compatibility happens in this line.

Strongest: "Saturday 8pm BST / 3pm ET, weekly, holds across DST. 5e. US East Coast through Central Europe welcome. Pacific time players please flag in your application that you're committing to a 12pm local start."

Anchored on the weekend slot transatlantic tables actually hold. DST handling stated. Implicit audience map (rules out PT-only players who won't survive lunch sessions). Reader knows whether to apply before reading anything else.

Guildhall's listing form is being built to capture this structurally: the GM enters a single anchor time in their local zone, the form generates both endpoints automatically, and applicants see the time in their own zone before they click apply.