Telecom Network Carbon Emission Logs

This dataset provides granular, timestamped logs of carbon emissions from telecom network components, including energy consumption, emission calculations, component details, and location data. It enables telecom operators and sustainability teams to monitor, analyze, and optimize network energy usage for ESG compliance and sustainability reporting. The comprehensive structure supports identification of high-emission areas, trend analysis, and data-driven decision making for greener telecom operations.

  • last updated 4 Jan 2026
  • by GoMask
The brief that made it

ESG and sustainability reporting for telecom operators

Sample rows

preview · 8 of 90 rows · all 19 columns
log_idstringcomponent_typestringenergy_consumed_kwhfloatlocation_countrystringtimestampdatetimenetwork_component_idstringcomponent_namestringlocation_latitudefloatlocation_longitudefloatlocation_citystringlocation_statestringemission_factor_kgco2e_per_kwhfloatcarbon_emission_kgco2efloatmeasurement_period_startdatetimemeasurement_period_enddatetimeenergy_source_typestringoperator_idstringregionstringnotesstring
LOG-0001cell_tower925.7USA2024-06-12T09:15:23ZCOMP-CT-101Cell Tower Alpha34.0522-118.2437Los AngelesCA0.38351.772024-06-01T00:00:00Z2024-06-07T23:59:59ZgridOP-A1North AmericaRoutine weekly log
LOG-0002base_station1450.3UK2024-06-12T10:22:41ZCOMP-BS-202Base Station Echo51.5074-0.1278LondonEngland0.25362.582024-06-01T00:00:00Z2024-06-07T23:59:59ZgridOP-B2EMEAblank
LOG-0003router402.5France2024-06-12T11:47:12ZCOMP-RT-303Router Delta-748.85662.3522ParisIle-de-France0.1248.32024-06-01T08:00:00Z2024-06-02T07:59:59ZgridOP-C3EMEAblank
LOG-0004switch259.3Japan2024-06-12T08:36:59ZCOMP-SW-404Switch Omega35.6895139.6917TokyoTokyo0.46119.282024-06-03T00:00:00Z2024-06-03T23:59:59ZsolarOP-D4APACSolar backup in use
LOG-0005data_center10500.4Germany2024-06-12T12:12:05ZCOMP-DC-505Data Center Gamma52.5213.405BerlinBerlin0.424410.172024-05-25T00:00:00Z2024-06-07T23:59:59ZgridOP-D4EMEAQuarterly check
LOG-0006cell_tower1120.5USA2024-06-12T13:11:36ZCOMP-CT-106Cell Tower Beta40.7128-74.006New YorkNY0.41459.42024-06-02T00:00:00Z2024-06-08T23:59:59ZgridOP-E5North Americablank
LOG-0007router388.9Russia2024-06-12T14:00:00ZCOMP-RT-304Router Sigma55.755837.6173MoscowMoscow0.48186.672024-06-09T00:00:00Z2024-06-09T23:59:59Zdiesel_generatorOP-F6EMEADiesel generator test
LOG-0008base_station790.2India2024-06-12T15:23:45ZCOMP-BS-208Base Station Zeta19.07672.8777MumbaiMaharashtra0.75592.652024-06-05T00:00:00Z2024-06-11T23:59:59ZgridOP-G7APACblank

What the 90 rows show

from the 90-row sample

Data_center (component type) stands out: mean energy_consumed_kwh is 10,075, against 432.9 for the rest.

  • 399.8median energy_consumed_kwh
  • 3regions
  • 6energy source types
  • 0.31median emission_factor_kgco2e_per_kwh
  • 113.9median carbon_emission_kgco2e
Mean energy_consumed_kwh by component_type90 rows
010k20k676.1cell_…18 rows862.1base_…18 rows213.8router18 rows119.5switch18 rows10,075data_…12 rows13.0other6 rows
energy_consumed_kwh90 rows, in bands of 2,000
040807800065108,00014kenergy_consumed_kwh →

Median 399.8, from 9.4 to 12,500.

location_country90 rows · top 10 of 33 values
  1. USA8
  2. Germany6
  3. Spain6
  4. Italy5
  5. Japan4
  6. Sweden4
  7. Finland4
  8. Czech Republic4
  9. Switzerland4
  10. UK3
19 columns by typefrom the column list below
  • string 11
  • float 5
  • datetime 3

Columns

19 columns in three groups
blueprint · 19 columns
columntypedescriptionexample
Text 11 columns
log_idstringUnique identifier for each carbon emission log entryuniqueLOG-0001
network_component_idstringUnique identifier for the telecom network component (e.g., cell tower, router, switch)COMP-CT-101
component_typestringType of network component (e.g., cell_tower, base_station, router, switch, data_center)6 valuescell_tower
component_namestringHuman-readable name or label for the network componentoptionalCell Tower Alpha
location_citystringCity where the network component is locatedoptionalLos Angeles
location_statestringState or province where the network component is locatedoptionalCA
location_countrystringCountry where the network component is locatedoptionalUSA
energy_source_typestringType of energy source powering the component (e.g., grid, solar, wind, diesel_generator)6 values · optionalgrid
operator_idstringIdentifier for the telecom operator or company responsible for the componentoptionalOP-A1
regionstringGeographical region or operational area (e.g., North America, EMEA, APAC)3 regions · optionalNorth America
notesstringAdditional comments, observations, or context for the log entryoptionalRoutine weekly log
Numbers 5 columns
location_latitudefloatLatitude coordinate of the network component's location-90 to 90 · optional34.0522
location_longitudefloatLongitude coordinate of the network component's location-180 to 180 · optional-118.2437
energy_consumed_kwhfloatAmount of energy consumed by the component during the measurement period (in kilowatt-hours)0 or more925.7
emission_factor_kgco2e_per_kwhfloatEmission factor used to calculate CO2 equivalent emissions (kgCO2e per kWh), based on local energy mix0 or more0.38
carbon_emission_kgco2efloatTotal carbon emissions produced by the component during the measurement period (in kilograms CO2 equivalent)0 or more351.77
Dates and times 3 columns
timestampdatetimeDate and time when the emission measurement was recorded2024-06-12T09:15:23Z
measurement_period_startdatetimeStart datetime of the measurement period for this log entry2024-06-01T00:00:00Z
measurement_period_enddatetimeEnd datetime of the measurement period for this log entry2024-06-07T23:59:59Z

Use it for

  • median energy …399.890 rowsmean energy consumed …676.1cell…862.1base…213.8rout…119.5swit…

    A telecommunications dashboard

    Energy_consumed_kwh by component_type and a breakdown of location_country. Excel, Power BI or Tableau.

  • Why do the 12 data_center rows have a mean energy_consumed_kwh of 10,075?

    A root-cause class exercise

    Hand out the rows and one question. The answer is in the data, not in the brief.

  • A software demo

    Believable logs with timestamp, network_component_id and component_type to fill a screen in front of a buyer.

Not quite right?

Make it yours.

Same 19 columns, your size and your rules. See 20 rows before you pay.

Preview 20 rows free

1,000 rows: $1.99 · 10,000: $12.99One-time. No subscription. All prices

This dataset90 rows19 columns
Yours1,000 rows19 columnslocation_latitude: UK only

blueprint · telecom-network-carbon-emission-logs

Behind this dataset

Same schema. As many rows as you need.

These 90 rows came out of a blueprint — 19 columns with generation rules behind each one. Open it in Data Factory to retune a column, add your own, wire in foreign keys, and run it at the size you actually need.

Rules it was built with
  • Each log entry represents a daily emission total per network site.
  • Include energy source types (renewable, grid, diesel) for each record.
  • Flag entries exceeding internal emission thresholds.
  • Capture both direct (scope 1) and indirect (scope 2) emissions.
  • Ensure consistency in units (kg CO2 equivalent).
Rows
Open the blueprint in Data Factory

1 credit per row. Preview 20 rows free. Buy rows for the full run.

Exports
CSV, JSON, JSONL, Parquet, SQL, Excel, TSV, XML
Licence
yours to use, including commercially
API slug
telecom-network-carbon-emission-logs

What should your data show?

Preview 20 rows free
No signup. No card.