The vessel skips the port
Your box lands elsewhere on the coast and the tariff that applies is the one where it landed.
Who pays depends on the cause: the carrier for its own schedule change, the shipper for a late gate-in.
Port profile · Norfolk, Virginia · figures read 07/26–07/29/2026
Port of Virginia has no volume figure in our reading and therefore no place in any size table here — and the number it does have is more interesting than a position would be. The $260 median first paid day on this page belongs to a category rather than to this port: six tariff lines price it, and not one of them writes its name.
That is why the figure is identical to Savannah’s to the dollar, along with the range and the spread. The same six group lines price both ports, and Savannah’s seventh line — the one that does name it — sits exactly at the median and moves it by nothing. Against the port that carriers do name, and name more often than any other, the contrast is worth a page of its own — it is linked above.
Nine US import demurrage tariffs · read 07/28–07/29/2026.
Port of Virginia is singled out by none of the nine carriers. Only two US ports are given their own free-time line anywhere in those documents — New York by COSCO and Savannah by Yang Ming — and this port shares Savannah’s rate group without sharing its carve-out.
Port of Virginia also has no authority rule we could locate, which is weaker than the cell on the Los Angeles or New York profiles where the document at least ranks in the port’s own results. The three start hours this site holds belong to other ports and are shown below labelled with whose they are.
How this profile is built · what we are paid
Container discharged at Norfolk · the free time comes from a group line that never names this port
| Whose tariff | Scope | The clock starts | Source · read |
|---|---|---|---|
| Georgia Ports Authority | Savannah, Rule 34-025 | first 12:01 AM after discharge | GPA Rule 34-025 · read 07/26/2026 |
| Maersk | Los Angeles and Long Beach imports | first 3:00 AM after discharge | Maersk, USA Imports · read 07/26/2026 |
| Seaboard Marine | US imports | first 08:00 of the first working day after discharge | Seaboard Marine, 11/05/2024 · read 07/26/2026 |
Port of Virginia carries one number on this stack and five empty lines, and the number needs its caption more than any other figure on this site: $260 is the residual group’s rate, from six lines that price ports the documents decline to name. Range $165 to $300, spread 1.8 — identical to Savannah’s for the same reason.
The empty lines are empty for two different causes. Terminal storage, terminal handling, local fees and chassis are our search at this port. Drayage is unpublished at every port in the country, which is a different kind of nothing.
What a 40-foot import container picks up at Norfolk, and how much of it we can price
What terminal handling costs where anyone publishes it: what terminal handling costs by port. The same stack ranked across every port, where the tariffs do name one: the cost stack ranked port by port.
Nine US import demurrage tariffs · read 07/28–07/29/2026.
| Charge at Norfolk | Billed by | Owed by | The document that sets it | Amount |
|---|---|---|---|---|
| Carrier demurrage | Ocean carrier | Consignee or the counterparty named on the invoice, not both | the carrier’s US import tariff, through a group that does not name this port | $260 median · $165–$300the category’s figure, not this port’s ownsix group lines · read 07/28–07/29/2026 |
| Terminal storage | The marine terminal | Cargo interest, via the carrier | a terminal tariff we have not read | not checked yetgap A, at all three terminals |
| Terminal handling | Ocean carrier | Whoever the Incoterm assigns | the carrier’s tariff, by port | not checked yet |
| Local fees | The port authority or the terminal | By fee | a fee schedule we have not located | not checked yetgap J |
Port of Virginia appears in the results as a multi-terminal system, and three abbreviations travel with the dwell figures: POV, NIT and VIG. None is expanded here. We have not opened a source that defines them, and a wrong expansion is the kind of error a reader carries into a booking.
| Code as it appears | What it stands for | Address | Gate hours and appointments |
|---|---|---|---|
| POV | not checked yetnever expanded from memory | not checked yetgap H | not checked yet |
| NIT | not checked yet | not checked yetgap H | not checked yet |
| VIG | not checked yet | not checked yetgap H | not checked yet |
Port of Virginia appears to publish the thing the dwell ranking says nobody publishes: a table that says which dwell each figure is. What survives in our capture is its structure — gate movements separated from rail movements, across three terminals — and not one of its values.
That is why the status below is located rather than read. A figure of 45 hours appears in the same material and which cell it belongs to does not survive either, so it is reported as an observation and adopted as nothing.
| Figure | What it measures | Status of the number |
|---|---|---|
| found, not read | a table separating gate from rail dwell across three terminals — at this port | structure located in the results; no value readseen 07/26/2026 |
| 45 hourswhich cell of that table it belongs to does not survive in our capture | unknown — reported, not adopted | observation about the resultsseen 07/26/2026 |
| found, not read | a live cameras and map page for this port | located, not openedgap E |
| 3.1 to 6.75 days | the spread at Los Angeles in one season — another port’s | quoted in the market, no documentsearch results · read 07/26/2026 |
| about 20 hours to 9.1 days | the spread at Savannah across three measures — another port’s | quoted in the market, no documentsearch results · read 07/26/2026 |
A dashboard is a snapshot; a table that labels which dwell each figure is, is what this subject actually needs. Opening the one that appears to sit at this port is the cheapest win available on the whole site for that gap. Which ports are backed up right now, and on which measure: which ports are backed up right now.
Port of Virginia local fees: not checked. The two rows carrying figures below belong to other ports and are labelled with them, so the shape of the missing row is visible — one is a fee on the truck, the other a charge by the day.
| Fee | Port | Amount | Who pays |
|---|---|---|---|
| Any local fee at this port | Norfolk | not checked yetgap J | not checked yet |
| Clean Truck Fund rate | Los Angeles, for contrast | $10 per TEU · $20 over 20 ftPort of Los Angeles · read 07/26/2026 | Motor carrier, passed through |
| Sustained Import Dwell Fee | Houston, for contrast | $45 per unit per day from day 8Port Houston · read 07/26/2026 | Cargo interest, billed by the port itself |
Port of Virginia scores badly on seven of these eight rows and may lead the entire site on the eighth. That is unusual enough to state plainly: on dwell this port appears to publish more than any port we have profiled, and it is entered below as located rather than read, which is what keeps the ledger honest.
| What an importer needs | Published? | Read by us? |
|---|---|---|
| Dwell, broken down by terminal and movement | apparently yes — a labelled table, which no other port here offers | found, not readgap E |
| A live operations view | yes — a cameras and map page | found, not read |
| The port authority’s own tariff | not checked yetnever located — gap B | not checked yet |
| Free time in days | not checked yet | only through a group that does not name this portnine US import demurrage tariffs · read 07/28–08/01/2026 |
| The hour the count starts | not checked yet | not checked yet |
| Container volume, dated | not checked yetgap D | not checked yet |
| Terminal addresses and gate hours | not checked yetgap H | not checked yet |
| A local fee schedule | not checked yetgap J | not checked yet |
| Located but unread: two. Read: none. This ledger ranks our reading as much as anyone’s disclosure, and on the first row it says a wave 1 port may be ahead of every port we have read properly. | ||
The East Coast ports compared on what can actually be compared: the East Coast ports compared.
Port of Virginia routes no inland market in our catalogue — unlike Savannah, Long Beach and Houston, no gateway page here points at it. That is a property of our map rather than of the port, and it is said that way rather than implying this port serves nowhere inland.
| Destination | How the box moves | Rate |
|---|---|---|
| Any inland market | road, or rail from a ramp we have not named | not publishedgap F — no comparable drayage set exists at any US port |
| A named rail ramp | not checked yet | not checked yetno ramp is named for this port in anything we hold |
| A gateway page on this site | not applicable | not applicableour map routes no market through this port yet |
Why the road leg has no figure at any US port: it is the one line of the five that nobody publishes in comparable form.
Your box lands elsewhere on the coast and the tariff that applies is the one where it landed.
Who pays depends on the cause: the carrier for its own schedule change, the shipper for a late gate-in.
It stays on the quay while the ship sails, and the cause decides the payer.
Carrier for overbooking; shipper for late gate-in or missing paperwork.
This is the local one. Your rate here comes from a residual group, so a carrier can revise any enumeration anywhere in its tariff and move the number that applies to your box without writing the name of this port.
Cargo interest — and the only defence is asking which group line was applied.
Charges do not stop accruing because nobody collects the box.
The named consignee, and the liability survives the abandonment.
Both of the first two have their own page: when the ship skips your port and what to do when the box will not move.
Port of Virginia demurrage arrives on a carrier’s invoice, not the port’s, and that invoice answers to a federal rule: 46 CFR Part 541, in force since 05/28/2024. The rule has been before the D.C. Circuit twice since, and the decision of 09/29/2025 changed who may be billed — so the text to read is the current one at eCFR, not a summary of the 2024 announcement.
The sequence specific to this port comes before any of that: establish which group line the carrier applied, ask for that group’s definition, and check that your port falls inside it. Here the definition is the entire basis of the charge, because nothing in the tariff names the port itself.
What the invoice has to contain, and how the dispute runs: the federal rules your invoice has to meet.
Descriptive, not legal advice. The tariff and the invoice in your own file govern your case.
Port of Virginia sits in a metro the results call Hampton Roads, and we have not counted it in the Federal Maritime Commission’s register of ocean transportation intermediaries. Two port areas have been counted — 95 organisations at Los Angeles and Long Beach, eleven at Savannah — and both counts belong to those two port areas rather than to this one. A register addressed by office location and a port carrying four names are a poor fit for each other, which is worth saying before anyone counts.
FMC OTI register download · read 07/28/2026.
Not even located for this port: the port authority tariff, the terminal tariffs, a volume release with a period, and the local fee schedule. How each status is defined: how every figure here is sourced.
A median of $260 for the first paid day across six tariff lines, with a range of $165 to $300 — and none of those six lines names this port. The figure is the rate carriers apply to ports they do not name separately, so it was set without this port specifically in view.
Because they are the same six lines. Savannah has a seventh that names it, and its first paid day is $260, so it sits at the median and moves nothing. Two ports sharing a figure to the dollar is a fact about the group rather than about either port.
One place. Every carrier tariff we read calls it Norfolk and this catalogue calls it Virginia, and the results add Port of VA and Hampton Roads. Search your own tariff for Norfolk; searching it for Virginia will return nothing.
We have not read that. The results name all three as Virginia ports and the capture carries three terminal abbreviations alongside the dwell figures, which is consistent with a multi-terminal system — but consistent is not read, and a booking naming one of them needs the answer before anything here applies.
There appears to be a published table separating gate from rail movements across three terminals, and we have not opened it. A figure of 45 hours appears in the results and which cell it belongs to does not survive in what we captured, so it is reported and not adopted.
That is precisely what makes it valuable. Five different things are called dwell across this site and no other publisher says which one they mean; this source appears to label them. Until it is opened we can say the labels appear to exist and nothing about the numbers.
Google reports that the word is absent from documents it ranked, on a query that names it. It is the third time on this site the engine's own message has been the most useful thing in a result set, and it is a reminder that a document containing the word would not necessarily be measuring the same thing.
Unknown to us. No port authority document has been located and no carrier singles this port out for free time — the only two any of the nine name that way are New York and Savannah, and this port shares Savannah's rate group without sharing its carve-out.
Our map routes none through it, unlike Savannah, Long Beach and Houston, which each feed a gateway page. That is a property of our map rather than of the port, and no drayage rate set exists for any US port to answer the question with.