Port Jersey
Freight transport facility in New Jersey, USA

Port Jersey, officially the Port Jersey Port Authority Marine Terminal and referred to as the Port Jersey Marine Terminal, is an intermodal freight transport facility that includes a container terminal located on the Upper New York Bay in the Port of New York and New Jersey. The municipal border of the Hudson County cities of Jersey City and Bayonne runs along the long pier extending into the bay.
The facility was created between 1972 and 1976 and acquired by the Port Authority of New York and New Jersey in July 2010. CMA CGM operates a post-panamax shipping facility at this terminal under the name Port Liberty Bayonne.
Much of Port Jersey is part of United States Foreign-Trade Zone 49. Most of the area in and around the facility is restricted, though a walkway along its northern side is accessible to the general public and may eventually connect with the Hudson River Waterfront Walkway. A very small bird sanctuary (specifically for the least tern) is also located on the promenade.
History
The area, east of the Greenville section of Jersey City was originally tidal marshes and white cedar swamps, and was first used for industrial purposes beginning in the 1800s.
The pier that become Port Jersey was created in the between 1972 and 1976 using landfill.
The facility was once known as the NorthEast Auto Terminal (NEAT) and was operated as a private auto import and export facility for several decades before its purchase in 2008 by the Port Authority of New York and New Jersey.
The public source identifies “Port Jersey” as freight transport facility in New Jersey, USA. This brief keeps that definition visible, then builds a research path around Port, Jersey and Freight.
Why this record matters
A short description can identify a subject without explaining its stakes. For “Port Jersey”, the useful work is to connect “freight transport facility in New Jersey, USA” to the records capable of establishing context and consequence.
Vocabulary and entity names are the principal evidence signals here, because they determine the precision of every later search. The source revision retrieved here is dated Jul 17, 2026. The linked authority identifier is Q7230722. Authority coordinates are 40.671, -74.074. 1 of 1 selected statements include explicit references; 0 carry qualifiers and 0 use preferred rank. The first chronological checks are 1972, 1976, 2010 and 2008.
Overview language is designed for orientation and should not be treated as a substitute for the evidence cited beneath it. The source lead contains qualifying language; that uncertainty should survive quotation, summary and reuse. Authority statements aid reconciliation but still require their own references, qualifiers and ranks to be checked.
How to read it
Use the entry as an orientation point, then follow its citations and revision history. Names, dates and institutional relationships should be checked against the original record.
- Subject orientation
- Search vocabulary
- Locating named sources
The closest primary source, responsible institution and strongest cited specialist reference.
Three-step research path
- Establish the record: confirm the title “Port Jersey”, its source revision and the description used here.
- Expand the search: follow Port Jersey primary sources, Port Jersey archive and Port research across catalogues and specialist indexes.
- Test the account: compare the strongest cited source with the responsible institution’s current record and note any disagreement.
Questions for further research
- Which source most directly establishes the central claim about “Port Jersey”?
- Which institution is responsible for the underlying evidence?
- What terminology or title could unlock a more precise catalogue search?
Search terms from this dossier
This entry incorporates text from “Port Jersey” on English Wikipedia. Contributors are listed in the page history. Text is available under the Creative Commons Attribution-ShareAlike 4.0 License. Selected authority identifiers and statements are retrieved from Wikidata under CC0; their references and qualifiers remain part of the verification path.