How Norway’s UDI waiting times work
GovWait preserves 19 complete, table-backed routes collected from 5 official UDI pages. Automated access is unavailable, so the values below are explicitly last-verified records rather than a claim about the source’s current figures.
What the figure does—and does not—mean
UDI presents these times as planning guides. They can change while an application is pending, and an individual case can take longer. The relevant official page explains which authority handles the route and where its clock starts; those details are not identical across visitor visas, residence cases and entry-ban matters.
GovWait therefore records the exact published value, UDI’s own update date, the official URL and our retrieval time. We do not calculate a personal decision date, treat the figure as a guarantee or infer anything about an application’s status.
Why the personalised guides are not in this release
UDI also uses question-and-answer guides for family, work, study, citizenship and several other topics. Their answers depend on selections such as application type and personal circumstances. This first Norway dataset uses only complete server-rendered tables whose routes are explicitly listed by UDI. It does not enumerate hidden parameters, invent country combinations or submit personal information.
Last-verified table-backed UDI routes
How ranges are represented
The stored UDI snapshot includes one value as a range: Visitor visa processed by an embassy in another country (15–29 days). GovWait keeps that wording unchanged in value_raw. Because the shared API also needs one normalized comparison number, value_days uses the range’s upper end. That conservative field is for sorting and charts; the full official range remains the value people should read.
History starts with a baseline
This Norway release created the first stored observation for each route. Those rows remain append-only while collection is paused. No new row, retrieval timestamp or change claim is created unless permitted source access is restored and a full validated refresh succeeds.