Multi-Utilities

Hugging Face Datasets - Utilities Search (75+ datasets)

Datadory delivers Hugging Face Datasets Utilities Search data covering all 75 repositories returned for the 'utilities' query: roughly 62 Nigerian Energy & Utilities tabular collections of 60k-220k rows each spanning billing, smart meters, grid load, outages and demand forecasting, four utility news corpora and one utility company-profile table - delivered as Parquet or CSV with every documented column intact.

Where it covers
Nigeria (DisCos, substations, plants); global utility firms elsewhere in the set
How far back
Billing months 2024-06 to 2024-12; collection captured 2026-08-21
How fine
Row-level records across 75 collections, 60k-220k rows per tabular set

What this dataset is

One search query, seventy-five collections, one delivery. Hugging Face Datasets - Utilities Search is the Hub's result set for the query 'utilities' as captured on 2026-08-21, and it is dominated by a single publisher: electricsheepafrica, whose Nigerian Energy & Utilities series contributes roughly 62 of the 75 hits, each a tabular collection shipping both a snappy-compressed Parquet file and a CSV twin with a README card stating row counts between 60k and 220k rows and an explicit column-schema table.

The series reads like a syllabus for emerging-market grid analytics. Twenty-one named themes hang under it: AI grid optimization, billing and payments, carbon footprint, commercial and industrial consumption, customer complaints, demand forecasting, dynamic pricing response, energy storage cycles, energy theft anomalies, equipment sensors, EV charging sessions, field technician logs, grid load, household smart meter, line losses, microgrid operations, outage fault logs, peak demand, plant emissions, power flow and power plant output.

The other thirteen results split two ways. gunnybd01 publishes four Utilities_News text corpora around small modular reactor coverage - showing 12.3k, 12.2k, 7.83k and 7.8k downloads at capture - and ttn1410/utilities_business_data adds a 47-row company-profile table with ticker, name, sector, industry, country, market_cap, currency, employees and description. Every row of every table arrives exactly as documented upstream; nothing is inferred from field names alone.

Sample rows

Three billing records exactly as they arrive, one per distribution company across tariff bands A through D:

customer_id       : CUS-0000000
disco             : Jos
billing_month     : 2024-12
tariff_band       : C
kwh               : 144.82
price_ngn_kwh     : 120.0
amount_billed_ngn : 17378.33
amount_paid_ngn   : 15947.79
paid_on_time      : false
arrears_ngn       : 1430.54

customer_id       : CUS-0000001
disco             : Kano
tariff_band       : A
kwh               : 134.48
price_ngn_kwh     : 206.0
amount_billed_ngn : 27702.87
paid_on_time      : true
arrears_ngn       : 2618.15

customer_id       : CUS-0000002
disco             : Enugu
billing_month     : 2024-06
tariff_band       : D
kwh               : 85.94
price_ngn_kwh     : 90.0
amount_billed_ngn : 7734.78
paid_on_time      : true
arrears_ngn       : 635.81

Note what three rows already demonstrate: the DisCo names are real distribution-company geographies (Jos, Kano, Enugu), tariff bands run A-D within a single month's sample, and payment behaviour arrives as a boolean with its naira consequence sitting beside it in arrears_ngn - so revenue-assurance math needs no derivation. Get a sample of this dataset cut to your themes and Datadory returns rows against your own question.

Field dictionary

The billing-and-payments table, typed and defined - ten columns verified from an actual file pull during research, not read off a field-name list:

FieldTypeDefinitionExample
customer_idstringAnonymized per-customer identifier, zero-padded to seven digits.CUS-0000000
discostringNigerian electricity distribution company serving the account.Jos
billing_monthstringMonth the bill covers, YYYY-MM format.2024-12
tariff_bandstringRegulatory tariff class assigned to the account.C
kwhfloat64Energy consumed in kilowatt-hours for the billing month.144.82
price_ngn_kwhfloat64Unit price applied, in naira per kWh.120.0
amount_billed_ngnfloat64Total billed for the month, in naira.17378.33
amount_paid_ngnfloat64Amount actually collected against that bill, in naira.15947.79
paid_on_timeboolWhether settlement landed within the allowed window.false
arrears_ngnfloat64Outstanding balance carried forward, in naira.1430.54

Beyond this table, the remaining sixty-plus collections carry their own documented schemas - sensor readings, outage events, charging sessions, technician logs - published as schema tables on each card rather than restated here. Those definitions travel with the sample on request, folded under additional fields on request so this page stays honest about what was verified versus what is documented-but-not-yet-pulled.

Coverage

  • Geographic: Nigeria for the main tabular block - distribution companies, substations and plants; the four news corpora and the company-profile table cover global utility firms instead.
  • Temporal: observed billing months run 2024-06 through 2024-12; the collection itself was captured 2026-08-21 with repo commits as recent as 2026-08-12.
  • Granularity: row-level records throughout - customer-month billing rows, individual news articles, one row per profiled utility company. Collection sizes range from under 1K rows to the 100K<n<1M band.

Read plainly: this is a snapshot of what the Hub surfaced for one query on one day, not a flowing operational feed. The billing months sit two years behind the capture date, which makes the tables vintage snapshots suited to schema work and benchmarking rather than current-state monitoring. Stacked dated deliveries are how any time series gets built here.

Delivery

API, files, or your warehouse. Daily, weekly, or hourly.

What teams do with it

ML model training. Sixty-plus themed collections give a benchmarking bench few industries can match: train a demand-forecasting model on one theme and validate generalization on grid load, peak demand and power flow. Row volumes of 60k-220k per theme keep training runs meaningful without a data-engineering project first.

Schema and product prototyping. The documented schemas cover nearly every artifact a utility-data product needs - customer-month billing rows, outage fault logs, EV charging sessions, field technician logs. Teams building utility analytics stand up realistic test environments in an afternoon instead of negotiating for production data.

Emerging-market revenue assurance. The billing table supports arrears analysis directly: amount_billed_ngn, amount_paid_ngn and arrears_ngn on every row mean collection-rate math is arithmetic, not estimation, across tariff bands A-D and multiple Discos.

Teaching and journalism. Four news corpora plus a company-profile table give students and writers real-shaped material without exposing actual customer records - useful precisely because the engineered origin is disclosable up front.

The personas who pull this most: data scientists and ML engineers building models, developers and data-product builders wiring utility schemas into products, market researchers mapping emerging-market utilities, and journalists, academics and students teaching with it. Industry context sits on the multi-utilities data hub; persona workflows at data scientists × multi-utilities, developers builders × multi-utilities and market researchers × multi-utilities.

How does it compare to other multi-utilities sources?

Within the multi-utilities shelf this is the volume play, answering a different question than the measured sources beside it. USGS Water Services - Instantaneous, Daily and Statistics REST APIs serve keyless readings for roughly 1.5 million monitored US sites, and World Bank Energy & Mining - World Development Indicators (Topic 5) ships 41 indicators across about 217 economies - official statistics built to survive scrutiny. This collection instead offers breadth and row volume: 75 collections, roughly 5-10 GB uncompressed, twenty-one named themes. Prototype and train here; cite the others when a number has to hold up. The full ranking sits on best multi-utilities datasets.

What are the limitations?

Stated up front, because they shape the analysis:

  • Engineered origin. The cards describe the collections as engineered by Electric Sheep Africa; whether rows are fully simulated or partially sourced from real DisCo operations is stated nowhere. Treat them as prototyping and benchmarking material, not regulatory or financial evidence.
  • Vintage snapshots. Observed billing months end at 2024-12 while the capture date is 2026-08-21 - there is no contractual refresh behind these tables.
  • Perishable perimeter. The 75-repo set reflects one query on one day; ranking drifts, so the exact composition will move between captures.
  • Concentration risk. Sixty-two of seventy-five hits come from one publisher, so a change to that single series reshapes the whole result set.

None of these surface at delivery time as surprises: the caveats ship attached, and Datadory flags which analyses they bite before anyone commits to one.

Why request this through Datadory

Because the interesting question is rarely "all seventy-five" - it is your themes, your tariff bands, your Discos. Requested samples come back cut to that shape with every documented column intact, Parquet twins included where the pipeline wants them. Scheduled deliveries land keyed on customer_id, so consecutive passes diff cleanly into arrears timelines and collection-rate trends even though the upstream tables themselves are vintage snapshots. The full catalog holds the rest of the multi-utilities shelf alongside this one.

Questions buyers ask

What is inside the 75-collection Hugging Face utilities search?

Three groups. Roughly 62 electricsheepafrica Nigerian Energy & Utilities tabular collections of 60k-220k rows each; four gunnybd01 utility news text corpora around small modular reactor coverage; and ttn1410's utilities_business_data, a 47-row table of utility company profiles running ticker through employee count.

What fields does the Nigerian billing table carry?

Ten typed columns: customer_id, disco, billing_month, tariff_band, kwh, price_ngn_kwh, amount_billed_ngn, amount_paid_ngn, paid_on_time and arrears_ngn. Types were verified from an actual file pull during research - kwh as float64, paid_on_time as boolean, monetary values in naira.

Are the Nigerian billing rows real customer records?

The cards describe collections engineered by Electric Sheep Africa and never state whether rows are fully simulated or partly sourced from real DisCo operations. Treat them as prototyping, schema-design and model-benchmarking material rather than regulatory or financial evidence.

Which topics does the collection span beyond billing?

Twenty-one named themes across the series: AI grid optimization, carbon footprint, commercial and industrial consumption, customer complaints, dynamic pricing response, energy storage cycles, energy theft anomalies, equipment sensors, EV charging sessions, field technician logs, line losses, microgrid operations, outage fault logs, peak demand, plant emissions, power flow and power plant output among them.

Can I get a sample cut to one theme?

Yes. Name the themes - billing and payments, household smart meter, outage fault logs, demand forecasting - and the sample returns those rows with every documented column intact, plus the Parquet twin if your pipeline prefers columnar files.

How much data is in the full delivery?

Seventy-five collections totalling roughly 5-10 GB uncompressed: about 62 tabular sets of 60k-220k rows each, four news text corpora whose download counters showed 12.3k down to 7.8k pulls at capture, and one 47-row company-profile table.

Notes on this record

  • One publisher, 62 tables electricsheepafrica's Nigerian Energy & Utilities series spans 21 named themes at 60k-220k rows each.
  • Verified dictionary Billing-table types confirmed from an actual file pull - float64 consumption and naira amounts, boolean settlement flag.
  • Snapshot, not stream Billing months end 2024-12 against a 2026-08-21 capture; time series come from stacked dated deliveries.
  • Quality scored 6/10 Below the catalog average of 7.81 - honest about engineered origins and the absence of a contractual refresh.

See the rows before you pay anything.

Name this dataset and we send real records from it — scoped to the fields you asked for.

See pricing