← All sources
LiveLive-testedOfficial public-page backend

Utilities / Electricity system operations

Georgian State Electrosystem live power balance and cross-border flows

Official live national grid frequency, consumption, generation by technology, aggregate import/export, and signed cross-border power-flow values. The public dashboard polls its JSON backends every 60 seconds.

01

Provenance and access

How the data is reached

Two unauthenticated JSON GET endpoints used by the official homepage dashboard.

Reuse status

Unclear; no explicit data reuse license or API terms found

02

Field-level detail

What is actually returned

livereferencederivedhistoricalunknown

Grid frequency

widget response; frequency unit confirmed by official dashboard.

1 fields
Field / pathTypeNull?ExampleMeaningFreshness
widgetnumberNo50.02Current grid frequency in hertzlive

National balance

typeSum fields; all power values displayed as MW.

9 fields
Field / pathTypeNull?ExampleMeaningFreshness
typeSum.timestampnull | stringYesnullIntended source measurement timestampNull during validation; always keep retrieval timelive
typeSum.hydroDatanumberNo2053.342773Hydroelectric generation, MWlive
typeSum.thermalDatanumberNo0Thermal generation, MWlive
typeSum.windPowerDatanumberNo2Wind generation, MWlive
typeSum.solarDatanumberNo0Solar generation, MWReturned by API but omitted from homepage summary tablelive
typeSum.importDatanumberNo11Aggregate import, MWderived
typeSum.exportDatanumberNo86.817204Aggregate export, MWderived
typeSum.totalConsumptionnumberNo1980.14502Total national consumption, MWderived
typeSum.totalGenerationnumberNo2055.342773Total national generation, MWderived

Cross-border flows

areaSum signed MW values. Official map uses sign to change arrow direction and displays absolute magnitude.

7 fields
Field / pathTypeNull?ExampleMeaningFreshness
areaSum.russiaSumnumberNo0Aggregate/other Russia interconnection flow, MWlive
areaSum.russiaSalkhinoSumnumberNo0Russia flow via Salkhino-labelled interconnection, MWlive
areaSum.russiaJavaSumnumberNo11Russia flow via Java-labelled interconnection, MWlive
areaSum.russiaNakaduliSumnumberNo0Russia flow via Nakaduli-labelled interconnection, MWlive
areaSum.azerbaijanSumnumberNo-11.231602Azerbaijan interconnection flow, signed MWlive
areaSum.armeniaSumnumberNo0Armenia interconnection flow, signed MWlive
areaSum.turkeySumnumberNo-75.585602Turkey interconnection flow, signed MWlive
03

Representative evidence

Sample records

Frequency

Retrieved 2026-07-22T13:44:48+04:00

JSON
{"widget":50.02}

Balance and flows

Retrieved 2026-07-22T13:44:48+04:00

JSON
{"typeSum":{"timestamp":null,"hydroData":2053.342773,"thermalData":0,"windPowerData":2,"solarData":0,"importData":11,"exportData":86.817204,"totalConsumption":1980.14502,"totalGeneration":2055.342773},"areaSum":{"russiaSum":0,"russiaSalkhinoSum":0,"russiaJavaSum":11,"russiaNakaduliSum":0,"azerbaijanSum":-11.231602,"armeniaSum":0,"turkeySum":-75.585602}}
04

Boundaries

Reliability, caveats, and privacy

What held up

  • Both endpoints returned HTTP 200 application/json
  • Values changed between requests
  • Client polling cadence and 3-minute stale threshold were verified in shipped JavaScript

What can go wrong

  • National system data, not household or district outages
  • typeSum.timestamp was null
  • Sign convention should be interpreted through the official map orientation
  • Undocumented endpoint
05

Cross-source possibilities

Ideas using this source