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.
Sample rows
preview · 8 of 90 rows · all 19 columns| log_idstring | component_typestring | energy_consumed_kwhfloat | location_countrystring | timestampdatetime | network_component_idstring | component_namestring | location_latitudefloat | location_longitudefloat | location_citystring | location_statestring | emission_factor_kgco2e_per_kwhfloat | carbon_emission_kgco2efloat | measurement_period_startdatetime | measurement_period_enddatetime | energy_source_typestring | operator_idstring | regionstring | notesstring |
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
| LOG-0001 | cell_tower | 925.7 | USA | 2024-06-12T09:15:23Z | COMP-CT-101 | Cell Tower Alpha | 34.0522 | -118.2437 | Los Angeles | CA | 0.38 | 351.77 | 2024-06-01T00:00:00Z | 2024-06-07T23:59:59Z | grid | OP-A1 | North America | Routine weekly log |
| LOG-0002 | base_station | 1450.3 | UK | 2024-06-12T10:22:41Z | COMP-BS-202 | Base Station Echo | 51.5074 | -0.1278 | London | England | 0.25 | 362.58 | 2024-06-01T00:00:00Z | 2024-06-07T23:59:59Z | grid | OP-B2 | EMEA | blank |
| LOG-0003 | router | 402.5 | France | 2024-06-12T11:47:12Z | COMP-RT-303 | Router Delta-7 | 48.8566 | 2.3522 | Paris | Ile-de-France | 0.12 | 48.3 | 2024-06-01T08:00:00Z | 2024-06-02T07:59:59Z | grid | OP-C3 | EMEA | blank |
| LOG-0004 | switch | 259.3 | Japan | 2024-06-12T08:36:59Z | COMP-SW-404 | Switch Omega | 35.6895 | 139.6917 | Tokyo | Tokyo | 0.46 | 119.28 | 2024-06-03T00:00:00Z | 2024-06-03T23:59:59Z | solar | OP-D4 | APAC | Solar backup in use |
| LOG-0005 | data_center | 10500.4 | Germany | 2024-06-12T12:12:05Z | COMP-DC-505 | Data Center Gamma | 52.52 | 13.405 | Berlin | Berlin | 0.42 | 4410.17 | 2024-05-25T00:00:00Z | 2024-06-07T23:59:59Z | grid | OP-D4 | EMEA | Quarterly check |
| LOG-0006 | cell_tower | 1120.5 | USA | 2024-06-12T13:11:36Z | COMP-CT-106 | Cell Tower Beta | 40.7128 | -74.006 | New York | NY | 0.41 | 459.4 | 2024-06-02T00:00:00Z | 2024-06-08T23:59:59Z | grid | OP-E5 | North America | blank |
| LOG-0007 | router | 388.9 | Russia | 2024-06-12T14:00:00Z | COMP-RT-304 | Router Sigma | 55.7558 | 37.6173 | Moscow | Moscow | 0.48 | 186.67 | 2024-06-09T00:00:00Z | 2024-06-09T23:59:59Z | diesel_generator | OP-F6 | EMEA | Diesel generator test |
| LOG-0008 | base_station | 790.2 | India | 2024-06-12T15:23:45Z | COMP-BS-208 | Base Station Zeta | 19.076 | 72.8777 | Mumbai | Maharashtra | 0.75 | 592.65 | 2024-06-05T00:00:00Z | 2024-06-11T23:59:59Z | grid | OP-G7 | APAC | blank |
| LOG-0009 | data_center | 8800 | Singapore | 2024-06-12T15:59:18Z | COMP-DC-510 | Data Center Theta | 1.3521 | 103.8198 | Singapore | Singapore | 0.52 | 4576 | 2024-06-01T00:00:00Z | 2024-06-07T23:59:59Z | grid | OP-H8 | APAC | First week of June |
| LOG-0010 | switch | 180.5 | USA | 2024-06-12T17:12:19Z | COMP-SW-407 | Switch Omega-2 | 37.7749 | -122.4194 | San Francisco | CA | 0.29 | 52.34 | 2024-06-07T00:00:00Z | 2024-06-07T23:59:59Z | solar | OP-I9 | North America | blank |
| LOG-0011 | cell_tower | 985.4 | India | 2024-06-12T18:04:10Z | COMP-CT-115 | Cell Tower Delta | 28.7041 | 77.1025 | Delhi | Delhi | 0.73 | 719.34 | 2024-06-03T00:00:00Z | 2024-06-09T23:59:59Z | wind | OP-J10 | APAC | blank |
| LOG-0012 | base_station | 720 | Italy | 2024-06-12T19:13:30Z | COMP-BS-212 | Base Station Sigma | 41.9028 | 12.4964 | Rome | Lazio | 0.34 | 244.8 | 2024-06-10T00:00:00Z | 2024-06-10T23:59:59Z | battery | OP-K11 | EMEA | Battery backup |
| LOG-0013 | router | 310.5 | Thailand | 2024-06-12T20:21:13Z | COMP-RT-309 | Router Lambda | 13.7563 | 100.5018 | Bangkok | Bangkok | 0.67 | 208.04 | 2024-06-02T00:00:00Z | 2024-06-02T23:59:59Z | grid | OP-L12 | APAC | blank |
| LOG-0014 | switch | 205.8 | Sweden | 2024-06-12T21:36:27Z | COMP-SW-412 | Switch Theta | 59.3293 | 18.0686 | Stockholm | Stockholm | 0.19 | 39.1 | 2024-06-11T00:00:00Z | 2024-06-11T23:59:59Z | wind | OP-M13 | EMEA | blank |
| LOG-0015 | data_center | 9700.2 | China | 2024-06-13T07:11:57Z | COMP-DC-520 | Data Center Sigma | 31.2304 | 121.4737 | Shanghai | Shanghai | 0.65 | 6305.13 | 2024-05-29T00:00:00Z | 2024-06-12T23:59:59Z | grid | OP-N14 | APAC | blank |
| LOG-0016 | cell_tower | 1058.2 | Italy | 2024-06-13T08:27:34Z | COMP-CT-120 | Cell Tower Gamma | 45.4642 | 9.19 | Milan | Lombardy | 0.18 | 190.48 | 2024-06-10T00:00:00Z | 2024-06-10T23:59:59Z | solar | OP-O15 | EMEA | blank |
| LOG-0017 | base_station | 1200 | China | 2024-06-13T09:35:19Z | COMP-BS-218 | Base Station Lambda | 23.1291 | 113.2644 | Guangzhou | Guangdong | 0.66 | 792 | 2024-06-04T00:00:00Z | 2024-06-04T23:59:59Z | grid | OP-P16 | APAC | blank |
| LOG-0018 | router | 390.3 | Australia | 2024-06-13T10:48:24Z | COMP-RT-315 | Router Omega-3 | -33.8688 | 151.2093 | Sydney | NSW | 0.45 | 175.64 | 2024-06-09T00:00:00Z | 2024-06-09T23:59:59Z | wind | OP-Q17 | APAC | blank |
| LOG-0019 | switch | 204.7 | Germany | 2024-06-13T11:18:57Z | COMP-SW-420 | Switch Zeta | 50.1109 | 8.6821 | Frankfurt | Hesse | 0.41 | 83.93 | 2024-06-05T00:00:00Z | 2024-06-05T23:59:59Z | battery | OP-R18 | EMEA | Short outage |
| LOG-0020 | data_center | 11000.8 | China | 2024-06-13T12:50:11Z | COMP-DC-530 | Data Center Omega | 39.9042 | 116.4074 | Beijing | Beijing | 0.61 | 6710.49 | 2024-06-01T00:00:00Z | 2024-06-07T23:59:59Z | grid | OP-S19 | APAC | Routine |
What the 90 rows show
from the 90-row sampleData_
- 399.8median energy_
consumed_ kwh - 3regions
- 6energy source types
- 0.31median emission_
factor_ kgco2e_ per_ kwh - 113.9median carbon_
emission_ kgco2e
Median 399.8, from 9.4 to 12,500.
- string 11
- float 5
- datetime 3
Columns
19 columns in three groups| column | type | description | example |
|---|---|---|---|
| Text 11 columns | |||
log_id | string | Unique identifier for each carbon emission log entryunique | LOG-0001 |
network_component_id | string | Unique identifier for the telecom network component (e.g., cell tower, router, switch) | COMP-CT-101 |
component_type | string | Type of network component (e.g., cell_tower, base_station, router, switch, data_center)6 values | cell_tower |
component_name | string | Human-readable name or label for the network componentoptional | Cell Tower Alpha |
location_city | string | City where the network component is locatedoptional | Los Angeles |
location_state | string | State or province where the network component is locatedoptional | CA |
location_country | string | Country where the network component is locatedoptional | USA |
energy_source_type | string | Type of energy source powering the component (e.g., grid, solar, wind, diesel_generator)6 values · optional | grid |
operator_id | string | Identifier for the telecom operator or company responsible for the componentoptional | OP-A1 |
region | string | Geographical region or operational area (e.g., North America, EMEA, APAC)3 regions · optional | North America |
notes | string | Additional comments, observations, or context for the log entryoptional | Routine weekly log |
| Numbers 5 columns | |||
location_latitude | float | Latitude coordinate of the network component's location-90 to 90 · optional | 34.0522 |
location_longitude | float | Longitude coordinate of the network component's location-180 to 180 · optional | -118.2437 |
energy_consumed_kwh | float | Amount of energy consumed by the component during the measurement period (in kilowatt-hours)0 or more | 925.7 |
emission_factor_kgco2e_per_kwh | float | Emission factor used to calculate CO2 equivalent emissions (kgCO2e per kWh), based on local energy mix0 or more | 0.38 |
carbon_emission_kgco2e | float | Total carbon emissions produced by the component during the measurement period (in kilograms CO2 equivalent)0 or more | 351.77 |
| Dates and times 3 columns | |||
timestamp | datetime | Date and time when the emission measurement was recorded | 2024-06-12T09:15:23Z |
measurement_period_start | datetime | Start datetime of the measurement period for this log entry | 2024-06-01T00:00:00Z |
measurement_period_end | datetime | End datetime of the measurement period for this log entry | 2024-06-07T23:59:59Z |
Use it for
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.
- Logs90LOG-0001925.7cell_tow…LOG-00021450.3base_sta…LOG-0003402.5router
A software demo
Believable logs with timestamp, network_
component_ id and component_ type to fill a screen in front of a buyer.
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.
- 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).
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