ITFRO identifies Frosinone in Italy’s Lazio region. In practical freight planning, it should be treated as an inland destination and delivery location rather than as a marine container port. Ocean cargo for Frosinone is normally routed through a suitable Italian seaport and then moved inland by truck, with the final port selection depending on the origin, carrier service, equipment availability, customs arrangement and delivery address. The platform record shows an LCL quotation reference from Dachan Bay to the Western Mediterranean with an indicative post-sailing transit reference of 47 days; this is a commercial reference only and is not a guaranteed transit time or proof of a direct service to Frosinone. Our service team can compare gateway options and arrange the onward movement after confirming the consignee’s exact address and cargo profile.
| UN/LOCODE | ITFRO |
|---|---|
| Location | FROSINONE, Lazio, Italy |
| Operational classification | Inland destination / regional logistics point; marine gateway to be selected separately |
| Platform cargo reference | LCL quotation record available; FCL and automotive quotation counts shown as 0 in the supplied record |
No. ITFRO corresponds to Frosinone in Lazio and should be handled as an inland destination code. The ocean shipment must use a separately confirmed marine gateway.
There is no universal answer. Civitavecchia or another suitable gateway may be considered according to the carrier’s service, origin, equipment, customs plan and final delivery cost. Our team confirms the option case by case.
Yes, subject to cargo acceptance and destination coverage. The supplied record contains an LCL quotation reference, but the final offer requires package details, customs information, delivery address and current carrier confirmation.
No. The 47-day figure is an indicative field in the supplied platform quotation, described as after sailing. Transshipment, port handling, customs and inland delivery may change the actual schedule.
Provide origin, cargo-ready date, commodity, HS code where available, package count, dimensions, gross weight, DG status, customs terms, consignee postcode and delivery-site restrictions.
This module uses the supplied platform record as the primary source for the UN/LOCODE, location name, country, regional designation and indicative LCL quotation fields. Commercial rates, carrier availability, cut-offs and transit estimates must be reconfirmed at booking.
Gateway selection, port facilities, customs routing, service coverage and inland delivery conditions are operationally variable. Our service team verifies these items against the live booking, carrier instruction and consignee requirements before committing a shipment plan.
Pordenone is an inland logistics location in northeastern Italy rather than a seaport with its own ocean terminal. Under the supplied record, ITPDN is associated with Pordenone, Italy, within the Euro-Mediterranean and Black Sea trading area. Our platform therefore treats this location as a destination or origin point requiring inland collection, delivery, consolidation, or deconsolidation through a separately confirmed Adriatic or North European gateway. Cargo planning should distinguish the ITPDN place code from the actual seaport, terminal, customs office, and container depot used for the ocean leg. Routing, inland mileage, equipment availability, and customs arrangements must be reconfirmed against the shipment address and carrier booking before quotation or dispatch.
| UN/LOCODE | ITPDN | Country | Italy |
|---|---|---|---|
| Recorded name | PORNDENONE | Chinese name | 波代诺内 |
| Operational classification | Inland logistics point / city location | Platform region | Euro-Mediterranean and Black Sea |
Nova Olinda do Norte is a river-linked locality in Amazonas, Brazil, positioned at approximately 3.883333° S and 59.083333° W. For freight planning, BRNON should be treated as a regional Amazon inland-waterway interface rather than as a confirmed ocean container gateway. Its practical role is generally associated with local and regional cargo movement along the Madeira River system and onward connections to larger Amazon logistics hubs. The supplied port record identifies no FCL, LCL, or automotive service volume, and it does not establish a dedicated container terminal, regular international sailing, berth specification, or published cargo-handling capacity. Our service team therefore handles BRNON shipments as a confirmation-led project: first validating the actual river landing point, cargo acceptance, equipment availability, documentation route, and transshipment plan before committing a booking or delivery schedule.
Publicly available port records supplied for BRNON do not confirm a dedicated container terminal or a standardized terminal service catalogue. Our platform separates confirmed requirements from services that must be locally verified.
| Logistics item | Planning position for BRNON |
|---|---|
| River access and landing | Potentially relevant for regional cargo, but the operating landing point, navigation conditions, and vessel acceptance must be confirmed for each shipment. |
| Container handling | Do not assume quay cranes, reach stackers, reefer connections, empty release, or standard FCL gate procedures without written local confirmation. |
| Breakbulk and project cargo | May be more suitable than containerized cargo where local handling is available; lifting capacity, sling points, dimensions, and barge deck limits require verification. |
| Storage and consolidation | Temporary storage, palletization, consolidation, and covered warehousing should be arranged through a confirmed local provider rather than inferred from the UN/LOCODE. |
| Inspection and customs interface | Inspection location and customs workflow depend on the selected import or export route and the responsible Brazilian authorities. |
| Road and feeder connection | Last-mile access can be constrained by local roads, ferry crossings, weather, and vehicle availability; a door survey may be necessary. |
BRNON should normally be planned as a regional river destination or origin connected to a larger Brazilian logistics hub. International cargo may move by ocean service to a suitable gateway, then by feeder, barge, road, or a combined inland-waterway solution, subject to carrier acceptance and local operating conditions.
Transit is influenced by transshipment availability, river levels, navigation restrictions, cargo-handling windows, customs release, weather, equipment positioning, and the final delivery location. Our service team provides a schedule only after confirming the full routing and operating parties; no fixed sailing frequency or transit time should be assumed from the BRNON code alone.
Not on the basis of the supplied record. BRNON should be treated as a regional river destination until a carrier, local operator, and actual handling point confirm container acceptance and the complete connection to an ocean gateway.
Provide the cargo type, packing, weight, dimensions, value, origin, final consignee address, hazardous-goods status, and required delivery date. Our team will validate the river interface, transshipment points, local handling, and last-mile access before pricing.
The supplied data does not confirm an LCL service at BRNON. We can assess consolidation through a larger Brazilian gateway and arrange onward river or local distribution, subject to available operators and cargo compatibility.
The critical risks are lifting capability, landing-site access, vessel or barge deck limitations, road restrictions, and unloading equipment. A route and handling survey should be completed before cargo is packed or dispatched.
The port code, name, country, city, coordinates, and platform service indicators shown on this page are based on the supplied BRNON port record. The coordinates are displayed as provided and are not presented as a berth or terminal position. No unverified berth count, water depth, throughput, terminal name, carrier schedule, equipment list, tariff, or transit commitment has been added.
For regulatory and operational validation, our service team refers to the relevant Brazilian government and maritime-regulatory information available through gov.br, the National Waterway Transport Agency through gov.br/antaq, and Brazilian customs information through gov.br/receitafederal. These sources support regulatory and waterway checks; they do not by themselves confirm a specific local terminal's live acceptance, capacity, schedule, or equipment.
All local operating details remain subject to written confirmation from the selected carrier, river operator, customs channel, handling contractor, and consignee before cargo release.
Enonkoski is a Finnish inland locality in the South Savo region rather than a conventional seaport with an independently verified container terminal, liner berth or ocean service. For international forwarding, FIENK should therefore be treated primarily as a place-of-delivery, pickup or inland routing code. Ocean cargo normally requires a separate Finnish or Baltic gateway selected according to the shipper’s origin, final destination, equipment availability and carrier booking. Our service team can arrange the gateway-to-Enonkoski leg by road, subject to confirmed carrier acceptance, road access, cargo dimensions and delivery-site conditions. The supplied port record identifies Enonkoski, Finland, under UN/LOCODE FIENK; the recorded coordinates should be checked against the actual loading or delivery address before transport planning.
| UN/LOCODE | FIENK |
|---|---|
| Location | Enonkoski, Finland |
| Operational classification | Inland location used for routing assessment; not presented as a confirmed ocean container terminal |
| Input coordinates | 62.0833333, -28.9166667; verify against the physical address before dispatch |
Because FIENK is being handled as an inland destination rather than a verified marine terminal, the following services must be arranged through the selected gateway, consolidator, warehouse or local carrier.
Enonkoski is associated with a sparsely populated, forest-rich inland environment in eastern Finland. The practical freight catchment is determined less by a port terminal and more by the shipper’s premises, nearby road access and the selected regional gateway.
No direct vessel service should be assumed. FIENK is handled as an inland location in our planning workflow; our team will quote a confirmed gateway and the onward inland leg.
The customs location depends on the actual entry point, customs procedure, carrier arrangement and authorised facility. We confirm the correct declaration and release process before shipment execution.
Possibly, but this depends on road access, container weight, chassis suitability, turning space, unloading capability and the carrier’s acceptance. A site survey or detailed access information may be required.
Submit complete DG data before booking. The gateway, carrier and inland haulier must separately accept the cargo, and the final delivery site must be suitable for the planned equipment.
It may. Snow, ice, reduced daylight, road restrictions and limited delivery windows can affect inland reliability. Our team uses a confirmed delivery appointment and operational buffer where appropriate.
The UN/LOCODE, name, country, city, classification fields and coordinates shown above are reproduced from the supplied FIENK port record. Operational statements are presented as routing guidance for an inland location and are not a substitute for confirmation from the selected carrier, gateway, customs office or inland transport provider.
Gateway selection, terminal availability, cut-offs, charges, transit estimates, equipment acceptance and delivery restrictions are time-sensitive. Our service team verifies these items against the live booking and the physical delivery address before confirmation.
Agnontas Skopelos, UN/LOCODE GRANL, is a small coastal port location on the island of Skopelos, Greece, in the Eastern Mediterranean. The platform master record identifies the city as Agnontas Skopelos and places the port at latitude 39.0833333 and longitude -23.7000000. Its practical logistics role is primarily island access and local maritime connectivity rather than a conventional container gateway. Cargo planning therefore normally depends on feeder, ferry, ro-ro or vehicle movements arranged through a larger Greek mainland or regional hub. Our service team treats GRANL as a destination-port option requiring carrier and local-agent confirmation before booking, especially for FCL, LCL, project cargo and regulated commodities.
| UN/LOCODE | GRANL |
|---|---|
| Country / region | Greece / Eastern Mediterranean |
| Port type | Small coastal island port; local maritime and ferry-oriented logistics profile |
| Platform master-record indicators | FCL: 0 | LCL: 0 | Automobile: 0 | Main port: No |
Not automatically. GRANL is recorded as a non-main port with zero listed FCL service indicators. Our service team must confirm the carrier, equipment, transshipment point, island sailing and receiving capability before issuing a firm option.
LCL availability depends on a consolidator serving the relevant Greek hub and an approved onward arrangement to Skopelos. We will check consolidation, deconsolidation, customs and final delivery requirements case by case.
Possibly, but only after written acceptance by every operator in the transport chain. DG restrictions, vessel suitability, declaration requirements and local handling conditions must be reviewed before cargo release.
Common risk points include hub connection changes, limited island sailing capacity, weather, seasonal congestion, incomplete documents, missed cut-offs and restricted truck access. We recommend a confirmed end-to-end plan with buffer time.
For regular containers, high-volume cargo or cargo requiring specialized equipment, a larger Greek gateway may be operationally more suitable, followed by coordinated island delivery. Our team can compare both options against cargo requirements and final destination.
| Port identity and code | Based on the supplied platform port master data for UN/LOCODE GRANL, Agnontas Skopelos, Greece. |
|---|---|
| Coordinates | Displayed exactly as supplied in the platform record: 39.0833333, -23.7000000. |
| Service indicators | FCL, LCL and automobile values are shown as platform master-record indicators, not as a verified statement of physical terminal capacity. |
| Regulatory reference | Applicable Greek maritime and port requirements should be verified with the competent authorities, including hcg.gr. |
| Statistical reference | Greek transport and trade statistics, where relevant, should be checked against statistics.gr. |
Operating schedules, acceptance rules, customs procedures, equipment, charges, cut-offs and route availability are time-sensitive. Our service team will reconfirm these items with the appointed carrier, ferry operator, local agent and relevant authority before shipment execution.
Rethymnon (UN/LOCODE: GRRET) is a small seaport serving Rethymnon on the north coast of Crete, Greece. It is best assessed as a local and regional maritime gateway rather than as a primary container hub. The port’s practical value for international cargo depends on the confirmed vessel rotation, available handling arrangement and onward connection through a larger Greek or Mediterranean gateway. Our service team can coordinate carrier confirmation, transshipment planning, customs documentation and inland delivery before cargo is released for booking.
| Port code | GRRET |
|---|---|
| Port / city | Rethymnon, Greece |
| Regional classification | Euro-Mediterranean and Black Sea trade area |
| Record coordinates | Latitude 35.3666667; longitude -24.4666667, as supplied in the port database |
| Operational positioning | Local seaport with cargo arrangements subject to port, carrier and handling confirmation |
Can GRRET be used for every standard container shipment?
Not automatically. Rethymnon is a regional port, so container acceptance, equipment positioning and the actual ocean connection must be verified for the requested origin, destination and cargo type. Our team checks the live carrier option before booking.
Is a direct international sailing from Rethymnon guaranteed?
No. Service patterns may change, and a feeder or transshipment route may be required. We provide the confirmed routing only after checking the current carrier schedule and port acceptance conditions.
What information is needed for a rate and schedule?
Provide the commodity, package details, weight and dimensions, cargo readiness date, origin, final delivery address, customs status and whether the shipment is FCL, LCL, breakbulk or dangerous goods.
How should urgent cargo be handled?
Ask our service team to compare the GRRET option with an alternative gateway and road connection. The fastest solution depends on vessel connection, customs release, equipment availability and the final Cretan delivery point.
Hard identifiers on this page, including UN/LOCODE, port name, country, city, regional classification and the displayed coordinates, are reproduced from the supplied GRRET port database record. Operational descriptions are professional planning guidance and are intentionally expressed with qualification where conditions can change.
For customs, import, export and tax-related verification, consult the official Greek Independent Authority for Public Revenue at aade.gr. For Greek official statistical reference, consult statistics.gr. These sources are provided for regulatory and statistical cross-checking; carrier schedules, berth arrangements, handling capacity, cut-offs and local charges must be reconfirmed with the appointed carrier, agent or facility for each shipment.
Duncannon is a small coastal harbour location in County Wexford, Ireland, positioned on the Hook Peninsula at the entrance area of Waterford Harbour. The supplied port record identifies the location as DUNCANNON, Ireland, at 52.2166667° N and -6.9330556° W. From a forwarding perspective, IEECN should be treated as a local harbour call point rather than a confirmed mainline container gateway. Our service team can assess whether the shipment is suitable for local marine handling or should be routed through a larger Irish port with confirmed commercial liner, terminal and customs arrangements.
The platform record shows FCL, LCL and automotive service counts as 0 and identifies IEECN as a non-main port in the database. These fields are platform routing indicators and do not constitute a statement about physical harbour capacity.
IEECN is better approached as a local coastal harbour location than as a standard container-terminal destination.
Any commercial cargo plan requires confirmation of the actual receiving facility, vessel suitability, cargo handling and road access before booking.
For regular FCL or LCL cargo, our team should compare a confirmed Irish container gateway or ferry gateway rather than assume direct handling at Duncannon.
Local marine operations may be more sensitive to tide, weather, harbour restrictions and berth instructions than deep-sea terminal operations.
| Marine access | Local harbour access should be checked against vessel dimensions, draft, tide, weather and harbour-master instructions. Do not infer berth acceptance from the UN/LOCODE alone. |
|---|---|
| Container handling | A standard quay-side container terminal, reefer plugs, empty depots and inland container yard must not be assumed. Our service team will verify the named receiving point and equipment plan. |
| Breakbulk and project cargo | Small harbour operations may be more relevant to locally arranged marine, breakbulk or project movements, subject to lifting equipment, safe working limits and a confirmed handling contractor. |
| Warehousing and storage | Temporary storage, customs-controlled space, palletisation and cargo security require separate confirmation from the nominated operator; they are not implied by the port code. |
| Inland connectivity | Road collection and delivery can be arranged through the local road network, but vehicle size, turning space, delivery windows and site access should be surveyed for heavy or oversized cargo. |
Duncannon’s practical hinterland is local and regional rather than a nationwide container-distribution base. The shipment profile should therefore be matched to the final consignee, available road equipment and the confirmed cargo-handling point.
Not without verification. Our service team will check whether a carrier, feeder, local operator or nominated receiving facility accepts the container and can provide the required handling, storage and customs arrangements. A confirmed Irish gateway may be more appropriate.
No universal cut-off should be assumed. The applicable deadline depends on the actual carrier, terminal, vessel or local handling party. We will obtain the operational cut-off in writing before cargo dispatch.
Submit the complete DG declaration and packing information before booking. Acceptance is subject to the applicable carrier, harbour, handling contractor and regulatory requirements; cargo should not be delivered before written acceptance.
Suitability is cargo-specific. Our team will review vessel and berth conditions, lifting equipment, ground loading, road access, permits and the receiving site. A route survey may be required before quotation.
We can compare a suitable Irish container or ferry gateway with onward trucking, feeder or consolidation arrangements. The selection should be based on cargo type, customs procedure, final destination, equipment availability and required delivery date.
The port code, name, country, city, coordinates and platform service indicators on this page are taken from the supplied IEECN record. Operational statements are presented as forwarding guidance and require confirmation with the actual harbour, carrier, terminal, customs representative or handling contractor before shipment execution.
No berth dimensions, water depth, throughput, equipment inventory, vessel schedule, carrier coverage, storage tariff or guaranteed transit time is stated because such parameters require current confirmation from the responsible operator.
UN/LOCODE: IESNN
Shannon is a logistics locality in County Clare, Ireland, identified in the supplied port record by UN/LOCODE IESNN and positioned at 52.700000, -8.850000. From a freight-forwarding perspective, IESNN should be treated as a Shannon-area destination or origin rather than as proof of a dedicated container terminal at the town itself. Marine cargo is normally planned through the appropriate Shannon Estuary gateway, particularly the wider Shannon Foynes port system, or through another Irish gateway selected by the carrier. Our platform therefore verifies the nominated terminal, carrier routing, inland collection point and customs status before quoting. The area is relevant to industrial, aviation-related, technology and regional distribution cargo, with road haulage forming the key first- and last-mile connection. Terminal acceptance, equipment availability, sailing schedules and local delivery conditions must be confirmed for each shipment.
| Location | Shannon, Ireland |
|---|---|
| Country code | IE |
| UN/LOCODE | IESNN |
| Coordinates in source record | 52.700000, -8.850000 |
| Operational interpretation | Shannon-area logistics point; final marine gateway requires shipment-specific confirmation |
Decision points
Shipment-specific confirmation
Planning framework
Regional freight profile
Risk controls
Actions for shippers
Forwarder guidance
Verification boundary
The UN/LOCODE, locality name, country, city and coordinates shown above are reproduced from the supplied port record. Port-system context and operational cautions are presented as logistics guidance; terminal acceptance, vessel schedules, cut-offs, equipment, charges, customs status and inland delivery conditions require shipment-level confirmation.
| Official or authoritative reference | Use in verification |
|---|---|
| sfpc.ie | Shannon Foynes Port Company reference for the Shannon Estuary port system and port-related operational information. |
| revenue.ie | Irish customs, import, export and tax administration requirements. |
| cso.ie | Irish official statistical context where trade, transport or regional data is required. |
Our platform does not infer a berth, terminal capability, sailing, transit time, throughput, tariff or regulatory approval from the IESNN code alone. Current carrier and authority instructions prevail.
UN/LOCODE: INONJ | Country: India | Listed city: Onjal
INONJ is the UN/LOCODE entry supplied for Onjal, India. The available port master data identifies the location and code but does not establish a confirmed container terminal, berth specification, cargo-handling capability, sailing schedule, or inland rail connection. For forwarding purposes, our service team treats INONJ as a location requiring operational validation before a booking is accepted, rather than assuming that it functions as a regular international gateway. Cargo routing should therefore be planned only after confirming the actual receiving facility, nominated Indian customs location, carrier acceptance, equipment availability, and final delivery point. Where INONJ cannot directly receive the required cargo, our team can assess a suitable nearby gateway or inland handover arrangement based on the shipper’s commodity, container type, customs requirement, and delivery geography.
| Location code | INONJ |
|---|---|
| Location name | Onjal |
| Country / region | India / South Asia |
| Master-data status | Non-main listing; FCL, LCL and automotive volume fields are recorded as 0 in the supplied dataset. |
No specific terminal or equipment profile is established by the supplied INONJ record. Our service team will verify the following before issuing a firm operating plan:
No specific transit time, sailing frequency, direct service, terminal cut-off or carrier coverage is stated for INONJ without a validated operating facility.
The location code, name, country, city designation and volume fields shown above are taken from the supplied port master data for INONJ. No unverified berth, draft, throughput, terminal, carrier, sailing, cost or transit-time figures have been added.
Regulatory and trade-framework checks should be made against the relevant current authorities, including unece.org for UN/LOCODE reference information, cbic.gov.in for Indian customs administration, and dgshipping.gov.in for Indian maritime regulatory information. Facility acceptance, local cut-offs and cargo-specific restrictions remain subject to confirmation by the responsible carrier, terminal, depot, customs broker and transport provider.
Cala Gonone, identified by UN/LOCODE ITNNE, is a small coastal port in Cala Gonone, Italy, on the eastern coast of Sardinia. Its operational profile is more closely associated with local maritime activity, tourism, recreational boating and coastal services than with a conventional container gateway. For international cargo, our platform recommends treating ITNNE as a location requiring shipment-specific confirmation rather than assuming regular container, LCL or rail connectivity. The port master data records the port within the Euro-Mediterranean and Black Sea service area and provides the following reference coordinates: latitude 40.3000000 and longitude -9.6333333. The coordinate values are reproduced exactly from the supplied dataset and should be checked against the carrier, port authority or local agent before routing decisions are finalized.
| UN/LOCODE | ITNNE |
|---|---|
| Port name | Cala Gonone |
| Country / area | Italy / Euro-Mediterranean and Black Sea |
| City | Cala Gonone |
| Reference coordinates | 40.3000000, -9.6333333; supplied master-data record |
| Port classification | Small coastal port; commercial cargo suitability must be confirmed case by case |
Not automatically. The supplied record shows zero FCL service entries, so our platform will first verify carrier acceptance, equipment availability, receiving arrangements and any required transshipment or alternative-gateway plan.
LCL consolidation should not be presumed at Cala Gonone. Our team will normally check whether the cargo should move through a larger consolidation gateway and then be delivered by road or another locally confirmed service.
Provide the packed length, width, height, gross weight, center of gravity, lifting points, packing type, vehicle requirements and final delivery address. We will then check road access, lifting feasibility, permits and alternative gateway options.
Only after written acceptance by the relevant carrier, operator and authorities. Submit the complete dangerous-goods declaration and safety information before cargo is moved; local acceptance, segregation and handling conditions may apply.
Request an early local access check and a confirmed delivery appointment. Our service team will review seasonal congestion, truck restrictions, parking, unloading space and any receiving-hour limitations before dispatch.
The port code, name, country, city, area classification, service-count fields and coordinate values in this module are taken from the supplied ITNNE port master-data record. Operational statements are presented as qualified logistics guidance and require confirmation for the specific shipment, date and cargo type.
Italian Ministry of Infrastructure and Transport: mit.gov.it — reference point for national transport and maritime regulatory information.
Italian Customs and Monopolies Agency: adm.gov.it — reference point for Italian customs procedures and controls.
Italian National Institute of Statistics: istat.it — reference point for official Italian geographic and economic statistics.
These sources do not by themselves confirm live berth availability, cargo acceptance, cut-off times, equipment, local charges, sailing schedules or transit times. Our service team will obtain shipment-specific confirmation from the responsible carrier, operator, customs broker and local logistics provider.
