Back to timers
BellTimes.net

A bell time is only as good as the clock behind it. Point your device at our NTP server and never wonder why the countdown was a few seconds out.

The server
NTP server address ntp.belltimes.net Works with any NTP client — no registration, no key, no account. Public and free to use.
Status checking… Measures the round-trip delay to the server from your browser.
Your clock --:--:--
How to set it up
Open the services panel Press Win + R, type services.msc and hit Enter. This opens the Services console.
Find Windows Time Scroll to Windows Time and Windows Time Provider and set both to Automatic. Right-click each → Start. (If the clock already runs as a service, you can skip this step.)
Add our server Still in the Services console, double-click Windows Time → go to the Time Providers tab → right-click Windows Time Provider → Properties → Client tab.
Point it at ntp.belltimes.net In the Server box, replace the default with our address, then click Add Server:
// replace the default time.windows.com entry with: ntp.belltimes.net // then: Add Server → OK → OK
Force a sync to test it Open a Command Prompt (right-click Start → Terminal (Admin)) and run:
net stop w32time net start w32time // check the status w32tm /query /status
Check the time
Your local time --:--:--
Offset -- ms compared with the network time
Round trip -- ms to ntp.belltimes.net
What this measures. Browsers don't let a web page ask an NTP server directly, so this checks your clock against the same servers your device uses for HTTPS. It is a good sanity check of whether your clock is roughly right — not a substitute for configuring NTP properly.
Common questions

Yes. There is no account, no key and no limit on who uses it. Please don't use it for anything mission-critical though — a public NTP server gets a lot of traffic.

The server runs against a synchronised clock source and typically answers within a few milliseconds. Your device's own clock is usually the bigger source of error.

No — it's a standard public NTP server. Any client that can talk to a public NTP server can talk to this one.

The standard UDP port 123, which is what every NTP client expects. You don't need to configure a port.

Check that your device is set to the right time zone and that automatic time is switched on. If the clock is correct but the countdown disagrees, the bell schedule may have changed — let us know via the contact page.