{"id":2979,"date":"2026-11-11T17:38:34","date_gmt":"2026-11-11T17:38:34","guid":{"rendered":"https:\/\/synmax.com\/energy\/lng-flows\/"},"modified":"2026-11-13T22:56:19","modified_gmt":"2026-11-13T22:56:19","slug":"lng-flows","status":"publish","type":"page","link":"https:\/\/synmax.com\/energy\/capabilities\/lng-flows\/","title":{"rendered":"LNG Flows & Cargo Tracking"},"content":{"rendered":"\n
\"\"<\/span>
\n
<\/g><\/svg><\/div>\n\"\"\n\n
\n\n
\n\n

Capability<\/p>\n\n\n

The pipeline and the tanker,
finally one story.<\/span><\/h1>\n\n\n

Feedgas to cargo, followed end to end.<\/p>\n\n<\/div>\n\n

<\/div>\n\n
\n\n

SynMax joins daily feedgas, plant status and cargo movement on one record for each facility, so a terminal running below capacity or a cargo sailing light is visible where it happens, not weeks later in two separate datasets.<\/p>\n\n\n

\n\n
Request a Demo<\/a><\/div>\n\n\n
All capabilities<\/a><\/div>\n\n<\/div>\n\n<\/div>\n\n<\/div>\n\n
<\/svg>Scroll to explore<\/span><\/div>\n<\/div><\/section>\n\n\n\n
\n\n
\n\n
\"Schematic:
Gas in, plant status and cargo out, joined to the same facility and timeline.<\/figcaption><\/figure>\n\n<\/div>\n\n<\/section>\n\n\n\n
\n\n
\n\n
\n\n

The Problem<\/p>\n\n<\/div>\n\n\n

The pipeline and the tanker are usually two different stories.<\/h2>\n\n\n

Feedgas nominations tell you what a terminal intends to pull. Vessel data tells you what left. Neither on its own explains a facility running below capacity or a cargo that sails lighter than expected.<\/p>\n\n\n

\n\n
\n\n
\"\"\/<\/figure>\n\n\n

Feedgas, daily<\/h3>\n\n\n

Pipeline deliveries into liquefaction are tracked day by day, so a drawdown shows up as it happens.<\/p>\n\n<\/div>\n\n\n

\n\n
\"\"\/<\/figure>\n\n\n

Cargo movement<\/h3>\n\n\n

Loadings and departures are followed from the berth, closing the loop between gas in and cargo out.<\/p>\n\n<\/div>\n\n\n

\n\n
\"\"\/<\/figure>\n\n\n

One continuous record<\/h3>\n\n\n

Feedgas and cargo are joined to the same facility and period, which is what makes a discrepancy visible at all.<\/p>\n\n<\/div>\n\n\n

\n\n
\"\"\/<\/figure>\n\n\n

Global terminals<\/h3>\n\n\n

Export and import facilities are covered on the same basis, so flows can be read across both ends of a trade.<\/p>\n\n<\/div>\n\n<\/div>\n\n<\/div>\n\n<\/section>\n\n\n\n

\n\n
\n\n
\n\n
\n\n
\n\n

One Timeline<\/p>\n\n<\/div>\n\n\n

A maintenance window, seen twice.<\/h2>\n\n\n

When a train goes down, the feedgas record dips and the cargo schedule thins out. Read separately, those look like two unrelated signals. On one timeline, they are the same event.<\/p>\n\n\n

Plant status is confirmed independently of what was nominated, so you can tell a train in maintenance from a plant that is simply pulling less.<\/p>\n\n<\/div>\n\n\n

\n\n
\"Illustrative
A dip in feedgas and a gap in departures, on the same timeline. Illustrative, not actual data.<\/figcaption><\/figure>\n\n<\/div>\n\n<\/div>\n\n<\/div>\n\n<\/section>\n\n\n\n
\n\n
\n\n
\n\n

How It Works<\/p>\n\n<\/div>\n\n\n

Pipe, plant, ship.<\/h2>\n\n\n
\n\n
\n\n
\n\n
\"\"\/<\/figure>\n\n\n

01 \/ FEEDGAS<\/p>\n\n<\/div>\n\n\n

Measure the intake<\/h3>\n\n\n
\n\n\n

Daily pipeline deliveries into each liquefaction facility establish what the plant is actually pulling.<\/p>\n\n<\/div>\n\n\n

\n\n
\n\n
\"\"\/<\/figure>\n\n\n

02 \/ FACILITY<\/p>\n\n<\/div>\n\n\n

Watch the plant<\/h3>\n\n\n
\n\n\n

Imagery and thermal signal confirm whether trains are running, in maintenance, or down, independent of what was nominated.<\/p>\n\n<\/div>\n\n\n

\n\n
\n\n
\"\"\/<\/figure>\n\n\n

03 \/ CARGO<\/p>\n\n<\/div>\n\n\n

Follow the ship<\/h3>\n\n\n
\n\n\n

Loadings and departures are tracked from the berth so volume out can be set against gas in.<\/p>\n\n<\/div>\n\n<\/div>\n\n<\/div>\n\n<\/section>\n\n\n\n

\n\n
\n\n
\n\n
\n\n
\"Illustrative
From the export berth to the import terminal. Illustrative routes, not actual cargoes.<\/figcaption><\/figure>\n\n<\/div>\n\n\n
\n\n
\n\n

Both Ends of the Trade<\/p>\n\n<\/div>\n\n\n

Follow the cargo, not just the terminal.<\/h2>\n\n\n

Export and import facilities are covered on the same basis, so a cargo can be read from the berth where it loaded to the terminal where it arrives.<\/p>\n\n\n

That closes the loop on the questions that matter commercially: where volume from a facility is actually going, and how this week compares with the same week last year.<\/p>\n\n<\/div>\n\n<\/div>\n\n<\/div>\n\n<\/section>\n\n\n\n

\n\n
\n\n
\n\n

Coverage<\/p>\n\n<\/div>\n\n\n

What is in the record.<\/h2>\n\n\n

Every stage of an LNG facility, from the pipe to the ship, tied to the same terminal and period.<\/p>\n\n\n

\n\n
\n\n

FEEDGAS<\/p>\n\n\n

Daily, by terminal<\/h3>\n\n\n

Pipeline deliveries into each liquefaction facility.<\/p>\n\n<\/div>\n\n\n

\n\n

FACILITY<\/p>\n\n\n

Train status<\/h3>\n\n\n

Running, in maintenance or down, from imagery and thermal signal.<\/p>\n\n<\/div>\n\n\n

\n\n

CARGO<\/p>\n\n\n

Berth to departure<\/h3>\n\n\n

Loadings and departures followed from each terminal.<\/p>\n\n<\/div>\n\n\n

\n\n

GEOGRAPHY<\/p>\n\n\n

Both ends of a trade<\/h3>\n\n\n

Export and import facilities covered on the same basis.<\/p>\n\n<\/div>\n\n\n

\n\n

HISTORY<\/p>\n\n\n

Year on year<\/h3>\n\n\n

Current feedgas read against the same period in past years.<\/p>\n\n<\/div>\n\n\n

\n\n

DELIVERY<\/p>\n\n\n

Where you work<\/h3>\n\n\n

Platform, agents, API, Snowflake or Excel.<\/p>\n\n<\/div>\n\n<\/div>\n\n<\/div>\n\n<\/section>\n\n\n\n

\n\n
\n\n
\n\n

In the Platform<\/p>\n\n<\/div>\n\n\n

Every terminal, end to end.<\/h2>\n\n\n

Feedgas against capacity, train status and cargo departures for each terminal, on one timeline.<\/p>\n\n\n

Pick a terminal to see what it is pulling, which trains are running and what has sailed, with every Gulf Coast facility on the map beside it.<\/p>\n\n\n

\"Illustrative
Illustrative dashboard with synthesized data.<\/figcaption><\/figure>\n\n<\/div>\n\n<\/section>\n\n\n\n
\n\n
\n\n
\n\n
\n\n
\n\n

In the Balance<\/p>\n\n<\/div>\n\n\n

Feedgas is a term in the gas balance.<\/h2>\n\n\n

LNG feedgas by terminal is one of the demand terms in the Hyperion supply and demand balance. Known maintenance is built in ahead of time, and new trains are tracked with satellite imagery and regulatory filings, so start dates follow what is happening on site.<\/p>\n\n\n

\n\n
See the balance<\/a><\/div>\n\n<\/div>\n\n<\/div>\n\n\n
\n\n
\"The
LNG feedgas sits alongside every other term in the balance.<\/figcaption><\/figure>\n\n<\/div>\n\n<\/div>\n\n<\/div>\n\n<\/section>\n\n\n\n
\n\n
\n\n
\n\n

Who Uses It<\/p>\n\n<\/div>\n\n\n

One record, three decisions.<\/h2>\n\n\n

The same terminal record answers different questions depending on the desk asking.<\/p>\n\n\n

\n\n
\n\n
\"\"\/<\/figure>\n\n\n

Gas and LNG traders<\/h3>\n\n\n

Read feedgas and plant status daily, ahead of the cargo record, and see a change as it starts.<\/p>\n\n<\/div>\n\n\n

\n\n
\"\"\/<\/figure>\n\n\n

Terminal and midstream operators<\/h3>\n\n\n

Set volume moving through the system against what was contracted and nominated.<\/p>\n\n<\/div>\n\n\n

\n\n
\"\"\/<\/figure>\n\n\n

Supply analysts<\/h3>\n\n\n

Feed terminal-level feedgas into the US gas balance, with maintenance and new trains built in.<\/p>\n\n<\/div>\n\n<\/div>\n\n<\/div>\n\n<\/section>\n\n\n\n

\n\n
\n\n
\n\n

Use Cases<\/p>\n\n<\/div>\n\n\n

What you can ask it.<\/h2>\n\n\n
\n\n
\n\n
\"\"\/<\/figure>\n\n\n

What is daily feedgas demand at this terminal?<\/h3>\n\n<\/div>\n\n\n
\n\n
\"\"\/<\/figure>\n\n\n

Is this facility running all trains, or is one down?<\/h3>\n\n<\/div>\n\n\n
\n\n
\"\"\/<\/figure>\n\n\n

How many cargoes have loaded here this month?<\/h3>\n\n<\/div>\n\n\n
\n\n
\"\"\/<\/figure>\n\n\n

Where are cargoes from this terminal actually going?<\/h3>\n\n<\/div>\n\n\n
\n\n
\"\"\/<\/figure>\n\n\n

How does current feedgas compare with the same week last year?<\/h3>\n\n<\/div>\n\n\n
\n\n
\"\"\/<\/figure>\n\n\n

Did the maintenance window end when it was supposed to?<\/h3>\n\n<\/div>\n\n<\/div>\n\n<\/div>\n\n<\/section>\n\n\n\n
\n\n
\n\n
\n\n

FAQ<\/p>\n\n<\/div>\n\n\n

Questions buyers ask.<\/h2>\n\n\n
\n\n
How is feedgas measured?<\/summary>\n

From daily pipeline deliveries into each liquefaction facility, which establish what the plant is actually pulling rather than what was nominated.<\/p>\n<\/details>\n\n\n

How do you know when a train is down?<\/summary>\n

Imagery and thermal signal confirm whether each train is running, in maintenance or down, independent of what the operator nominated.<\/p>\n<\/details>\n\n\n

Do you track where cargoes go?<\/summary>\n

Yes. Loadings and departures are followed from the berth, so volume out can be set against gas in and cargoes can be followed to where they actually go.<\/p>\n<\/details>\n\n\n

Are import terminals covered?<\/summary>\n

Yes. Export and import facilities are covered on the same basis, so flows can be read at both ends of a trade.<\/p>\n<\/details>\n\n\n

How does this connect to the gas balance?<\/summary>\n

LNG feedgas by terminal is one of the demand terms in the Hyperion supply and demand balance, with known maintenance and new trains built in.<\/p>\n<\/details>\n\n\n

How do I get the data?<\/summary>\n

In the platform, through agents, by API, in Snowflake or in Excel, so the answer arrives in the system your team already uses.<\/p>\n<\/details>\n\n<\/div>\n\n<\/div>\n\n<\/section>\n\n\n\n

\n
<\/div>\n\n
\n\n
\n\n

Get Started<\/p>\n\n<\/div>\n\n\n

Close the loop on a terminal you follow.<\/h2>\n\n\n

Name an export facility and we will show you its feedgas record next to its cargo history, on the same timeline.<\/p>\n\n\n

\n\n
Request a Demo<\/a><\/div>\n\n\n
Explore Solutions<\/a><\/div>\n\n<\/div>\n\n<\/div>\n\n<\/section>\n","protected":false},"excerpt":{"rendered":"

The Problem The pipeline and the tanker are usually two different stories. Feedgas nominations tell you what a terminal intends to pull. Vessel data tells you what left. Neither on its own explains a facility running below capacity or a cargo that sails lighter than expected. Feedgas, daily Pipeline deliveries into liquefaction are tracked day […]<\/p>\n","protected":false},"author":1,"featured_media":0,"parent":3070,"menu_order":0,"comment_status":"closed","ping_status":"closed","template":"","meta":{"_acf_changed":false,"footnotes":""},"class_list":["post-2979","page","type-page","status-publish","hentry"],"acf":[],"_links":{"self":[{"href":"https:\/\/synmax.com\/energy\/wp-json\/wp\/v2\/pages\/2979","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/synmax.com\/energy\/wp-json\/wp\/v2\/pages"}],"about":[{"href":"https:\/\/synmax.com\/energy\/wp-json\/wp\/v2\/types\/page"}],"author":[{"embeddable":true,"href":"https:\/\/synmax.com\/energy\/wp-json\/wp\/v2\/users\/1"}],"replies":[{"embeddable":true,"href":"https:\/\/synmax.com\/energy\/wp-json\/wp\/v2\/comments?post=2979"}],"version-history":[{"count":3,"href":"https:\/\/synmax.com\/energy\/wp-json\/wp\/v2\/pages\/2979\/revisions"}],"predecessor-version":[{"id":3060,"href":"https:\/\/synmax.com\/energy\/wp-json\/wp\/v2\/pages\/2979\/revisions\/3060"}],"up":[{"embeddable":true,"href":"https:\/\/synmax.com\/energy\/wp-json\/wp\/v2\/pages\/3070"}],"wp:attachment":[{"href":"https:\/\/synmax.com\/energy\/wp-json\/wp\/v2\/media?parent=2979"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}