Singapore Port Congestion & Trade Signal Radar

Scrape Singapore-area vessel positions and add port congestion risk signals.

What This Actor Does

This Actor works like a Singapore marine traffic scraper with extra intelligence fields. It returns vessel rows from the Singapore port and Singapore Strait area, then enriches each row with congestion score, risk level, pressure signal, and a plain-English recommendation.

It answers:

• Which vessels are currently visible around Singapore port and the Singapore Strait?
• Is congestion pressure increasing?
• Are trade flows strong, normal, or weak?
• Are there disruption signals logistics teams should watch?
• Should teams take action now?

Simple Input

The default settings are ready to run. No AIS API key is required. AIS coverage includes Singapore port and the wider Singapore Strait area.

{
  "lookbackMonths": 24,
  "includeNewsSignals": true,
  "includeAIS": true,
  "maxVessels": 1000,
  "alertThreshold": 70
}

Input Fields

• lookbackMonths - Number of months to analyze.
• includeNewsSignals - Add shipping disruption news signals.
• includeAIS - Add vessel-density and slow-vessel signals.
• maxVessels - Maximum vessel rows to save. Default is 1,000.
• alertThreshold - Score level that triggers an alert.

Output

The Actor returns vessel rows, similar to a MarineTraffic scraper:

• 1 dataset result = 1 vessel
• Each vessel row includes Singapore port radar context, such as congestion score, risk level, pressure signal, and recommended action.
• The full Markdown intelligence brief is saved separately as REPORT.md.

Each vessel row can include:

• vessel_name
• mmsi
• imo
• vessel_type
• latitude
• longitude
• speed_knots
• destination
• observed_at
• is_slow_vessel
• is_stopped_or_waiting
• congestion_score
• risk_level
• trade_signal
• pressure_signal
• summary
• recommended_action

It also saves:

• REPORT.md
• SIGNALS.csv

Example Output

{
  "row_type": "vessel",
  "date": "2026-05-21",
  "observed_at": "2026-05-21T10:12:47.000Z",
  "port": "Singapore",
  "source": "MarineTraffic public AIS map scraper",
  "vessel_name": "EXAMPLE VESSEL",
  "mmsi": "563123456",
  "vessel_type": "Cargo",
  "latitude": 1.263,
  "longitude": 103.821,
  "speed_knots": 0.8,
  "is_slow_vessel": true,
  "is_stopped_or_waiting": true,
  "congestion_score": 71,
  "risk_level": "high",
  "trade_signal": "normal",
  "pressure_signal": "disrupted",
  "summary": "Singapore port pressure is elevated. Vessel-density or throughput indicators are above normal, and logistics teams should monitor potential delays.",
  "recommended_action": "Monitor freight bookings, ETA buffers, and possible routing alternatives over the next 7 days."
}

If AIS is unavailable, the Actor returns a single report row instead of vessel rows.

Use Cases

• Freight forwarders monitoring delay risk
• Importers and exporters watching supply-chain pressure
• Shipping analysts tracking Singapore port activity
• Market researchers monitoring Southeast Asia trade flow
• Newsletter writers creating shipping intelligence briefs
• Traders watching bunker and container activity

Notes

• Official port statistics are monthly.
• Vessel and news signals can change between runs.
• Each dataset result is normally one vessel row.
• The report still uses official port statistics and news signals, but those are saved as context instead of separate dataset rows.
• Result count depends on live vessel density and your maxVessels setting.
• Free preview runs are limited to 10 vessel rows.
• Pricing works naturally as results-based usage because vessel rows are the main dataset output.
• If a live source is unavailable, the Actor continues with the remaining sources and adds a warning.
• This Actor provides operational signals, not financial or logistics advice.