Long-Distance Planner
Distance is mostly arithmetic that nobody does. Two people in Berlin and New York do not lack love; they lack a shared evening. Once you write down both local clocks and both real bedtimes, a long-distance relationship stops being a feeling and becomes a schedule: a daily overlap that is usually shorter than you think, an evening overlap that is often zero, and a quarterly bill that almost nobody counts honestly. This tool does two things with that arithmetic. It finds the hours when you are both awake, splits them into the parts that are useful and the parts that are merely awake, and names the best two-hour slot of the day. Then it costs a real visit: the flights and the apartment, plus the SIM card, the airport taxi, the tips, the visa, the laundry, and the sixteen hours in transit that most people price at zero.
How to use it
Put both cities in with their UTC offsets. Use the offset that is true right now, including daylight saving if it is in force, because one hour of drift is one hour of your overlap and one more hour of somebody being awake at the wrong time.
Enter each wake time and bedtime as local hours: 7 for 07:00, 22.5 for 22:30. Be honest about the real bedtime rather than the ideal one. The distance between the ideal bedtime and the actual one is a large part of what long distance costs.
For the money, start with the visible cost of one visit, then add fixed hidden costs (SIM or eSIM, visa or entry fee, insurance) plus a daily amount for local transport, tips, snacks and souvenirs. The tool multiplies the daily part by the number of visit days.
Add your travel hours and what an hour of your time is worth to you. Travel time is a real cost: sixteen hours of flying and waiting is not free time, it is time the two of you are not in the same room.
Three common mistakes
- Forgetting to include the travel days in the length of the visit. A five day trip to New York from Berlin is seven days away from home. If the cost model counts five days of hidden costs but eight days of missing each other, the weekly budget will look better than it is.
- Pricing hidden costs at zero because the first visit did not have them. The SIM card, the airport taxi and the laundry are not one-off expenses. They repeat on every single visit, and they are the difference between a trip that looks like 1,450 and one that actually costs 1,705.
- Treating travel time as dead time instead of a cost. Sixteen hours round trip, valued at 24 an hour, is 384 per visit and 1,536 a year at four visits. That is the number most people forget entirely, and it is often larger than the tips and the visa combined.
- Assuming the overlap looks the same in both directions. With a six hour gap the window is 12:30 to 23:00 in one city and 06:30 to 17:00 in the other. The same 10.5 hours are an evening for one person and a long lunch for the other, which is why calls keep drifting to the wrong hour.
How the overlap is actually computed
The tool walks the 24 hour clock of city A in ten minute steps. For each step it converts the time into city B local time, then checks two simple awake windows: one for partner A and one for partner B. A window runs from the wake time to the bedtime, and if the bedtime is earlier in the day than the wake time the window wraps past midnight. Ten minute steps mean the answer is accurate to within ten minutes, which is far better than the guess most couples make.
Run the default example through it. Berlin is one hour ahead of UTC and New York is five hours behind, so partner B local time runs six hours behind partner A local time. Partner A is awake from 07:00 to 23:00 in Berlin, which is 01:00 to 17:00 in New York. Partner B is awake from 06:30 to 22:30 in New York, which is 12:30 to 04:30 in Berlin. The intersection is 12:30 to 23:00 Berlin time, which is 630 minutes, or 10.5 hours a day.
Now the part that matters. Of those 10.5 hours, 5.5 sit between 12:00 and 18:00 in Berlin, and 5.0 sit between 18:00 and 23:00 in Berlin. But those same 5 evening hours are 12:00 to 17:00 in New York: lunchtime for the other person. The tool therefore also counts a shared evening, defined as minutes when both of you are awake within three hours of your own bedtimes. With these numbers that figure is 0.0 hours, and that zero is the single most useful number the page produces.
The three numbers that decide whether a visit pays
A visit has three cost layers and couples usually only price the first one.
- Visible cost: 1,450. Flights, the apartment, food. The number everyone quotes, and the easiest to cut.
- Hidden cost: 255 per visit, 15.0 percent of the trip. A SIM or eSIM, the visa or entry fee, travel insurance, a pharmacy run, plus 30 a day for local transport, transfers, tips, snacks and souvenirs. On four visits that is 1,020 a year for things that do not appear on any receipt you show anybody.
- Travel time: 384 per visit. Sixteen hours of flying and waiting at 24 an hour. Over four visits that is 1,536 a year, and it is the hardest layer to reduce because it is the price of the distance itself.
Add them up and one visit costs 2,089 all in, four visits cost 8,356 a year, and that is 22.89 a day for every day of the year. Divide the annual figure by the hours of overlap you actually have, and one available overlap hour costs 2.18 a year. Use the daily figure rather than the annual one when you argue with yourself: 22.89 a day is easy to imagine, and so is the 8,356 that comes out of it.
Choosing an anchor instead of pretending the gap is not there
The goal of a long-distance week is not more hours. It is better hours. The daily 10.5 hour overlap already exists whether you use it or not, and most of it is daytime for one person. What changes outcomes is anchoring one or two evening slots a week and defending them, and the tool tells you what an anchor is worth.
Move one bedtime 90 minutes later, or wake one person 90 minutes earlier, and the daily overlap goes from 10.5 to 12.0 hours, a gain of 1.5 hours a day. That is not dramatic in isolation. Across a year it is 547 extra hours of shared awake time, which is more than three full weeks, for the price of one later bedtime. The same calculation works in the other direction: if you shift the other way and lose 1.5 hours a day, that is a week and a half of shared time disappearing quietly across the year.
Two practical rules fall out of the arithmetic. First, the best two-hour slot is the earliest window where both local clocks sit between 08:00 and 20:00, which is the one the tool names for you. Put the anchor call there and stop negotiating it every week. Second, if one of you moves to a new city, rerun the tool with the new offset before you agree on anything. Offsets change twice a year and the overlap you promised in January is not the overlap you get in July.
FAQ
Do I need my partner to know their exact bedtime for this to work?
What if one of us works night shifts?
Is a six hour gap workable?
Which cost should I reduce first?
Does this tool tell me whether we should stay together?
Limits of this tool
- This tool computes schedule overlap and money. It does not assess the relationship, the commitment, or the wellbeing of either partner, and no output on this page should be read as a verdict.
- Limits of this tool: offsets are entered by hand and daylight saving changes twice a year, so re-check the offsets after every clock change. Travel costs are averaged from what you type in, not quoted from any operator.
- The shared evening figure uses a three hour window before each bedtime. That is a convention, not a law. Couples with very different bedtimes can get a different number, and the daily overlap total never changes.
- Currency is whatever you enter; the tool does not convert. Prices for flights, SIM cards and visas differ by country and by season, and the real figures on the day will always be the ones on the booking page.