GMT+0 Time Zone Countries list - UTC+0 Time Now

UTC+0 time now

The local clock here equals the UTC clock. That makes UTC+0 the natural anchor for logs, timetables and international coordination: state a moment in UTC and nobody has to ask which country you meant.

Countries and cities on UTC+0

This offset holds more people than most of the western zones combined, thanks to West Africa and the British Isles. United Kingdom — London, Manchester, Glasgow and Belfast, on UTC+0 as Greenwich Mean Time in winter.

Ireland — Dublin and Cork, on the same winter schedule. Portugal — Lisbon and Porto in winter; the Azores sit an hour behind. Iceland — Reykjavík, on UTC+0 all year with no clock changes. Ghana — Accra, year-round.

Senegal — Dakar, year-round. Côte d'Ivoire — Abidjan, year-round. Mali, Burkina Faso, Guinea, Sierra Leone, Liberia, Togo, The Gambia, Mauritania — Bamako, Ouagadougou, Conakry, Freetown, Monrovia, Lomé, Banjul and Nouakchott, all fixed on this offset.

Morocco — Casablanca and Rabat during Ramadan, when the country steps back from its usual UTC+1.

Daylight saving on the reference line

The European members of UTC+0 treat it as their winter position. The UK, Ireland and mainland Portugal move to UTC+1 for the summer, so for roughly seven months of the year London is not on UTC+0 at all — a fact that trips up anyone who learned "London equals UTC" and stopped there.

The West African countries on this offset do not change their clocks. Accra, Dakar and Abidjan hold UTC+0 in every month. Iceland does the same, having decided that a country that far north gains little from shuffling an hour of a very uneven year.

Morocco is the interesting exception in the other direction: it normally sits on UTC+1, and steps back to UTC+0 for the month of Ramadan before returning. Its position on this offset is temporary and moves through the Gregorian calendar year by year.

Half the world writes its timestamps in UTC and half of Europe is on it only in winter — the reference line is the one place where "local time" is a genuinely bad idea.

Why UTC+0 is the one to write things in

If you are recording something rather than scheduling it, use this offset. The reasons are practical: It never shifts. There is no summer UTC, so a UTC timestamp means one moment forever. It removes ambiguity at the change dates, where a local hour can occur twice or not at all.

It converts cleanly to every other zone by simple addition or subtraction. It matches what most systems record internally, so no translation error creeps in between log and display. For scheduling with people, do the opposite: name their city. Machines want UTC; humans want somewhere they recognise.