Telecom Subscriber Usage Patterns
This dataset provides detailed, event-level telecommunications usage records for individual subscribers, including calls, SMS, and data sessions, enriched with device, location, and demographic attributes. It is ideal for customer segmentation, churn prediction, and targeted marketing analytics in the telecom industry.
Sample rows
preview · 8 of 200 rows · all 18 columns| subscriber_idstring | directionstring | data_volume_mbfloat | is_roamingboolean | subscriber_genderstring | event_idstring | event_typestring | event_datetimedatetime | duration_secondsinteger | sms_countinteger | counterparty_numberstring | cell_tower_idstring | location_citystring | location_statestring | location_countrystring | device_typestring | plan_typestring | subscriber_ageinteger |
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
| SUB0001 | outgoing | blank | false | female | EVT10001 | call | 2024-05-01T08:15:23Z | 120 | blank | +12045550121 | CT1001 | San Francisco | CA | USA | smartphone | postpaid | 28 |
| SUB0002 | incoming | blank | false | male | EVT10002 | sms | 2024-05-01T09:07:45Z | blank | 3 | +447911123456 | CT1002 | London | England | UK | feature phone | prepaid | 38 |
| SUB0003 | outgoing | 120.5 | true | female | EVT10003 | data | 2024-05-01T10:23:19Z | 900 | blank | blank | CT1003 | Berlin | Berlin | Germany | tablet | postpaid | 45 |
| SUB0004 | incoming | blank | false | male | EVT10004 | call | 2024-05-01T10:45:00Z | 35 | blank | +61123456789 | CT1004 | Sydney | NSW | Australia | smartphone | family | 52 |
| SUB0005 | outgoing | 512.75 | false | female | EVT10005 | data | 2024-05-01T11:32:11Z | 1800 | blank | blank | CT1005 | Toronto | ON | Canada | smartphone | prepaid | 23 |
| SUB0006 | outgoing | blank | false | female | EVT10006 | sms | 2024-05-01T12:01:37Z | blank | 5 | +33123456789 | CT1006 | Paris | IDF | France | feature phone | postpaid | 67 |
| SUB0007 | outgoing | blank | false | male | EVT10007 | call | 2024-05-01T12:45:22Z | 300 | blank | +4915112345678 | CT1007 | Frankfurt | HE | Germany | smartphone | family | 31 |
| SUB0008 | incoming | 2048.2 | false | other | EVT10008 | data | 2024-05-01T13:09:15Z | 2400 | blank | blank | CT1008 | Mumbai | MH | India | smartphone | postpaid | 19 |
| SUB0009 | incoming | blank | true | male | EVT10009 | sms | 2024-05-01T13:35:41Z | blank | 1 | +5511998765432 | CT1009 | São Paulo | SP | Brazil | feature phone | prepaid | 41 |
| SUB0010 | outgoing | blank | false | female | EVT10010 | call | 2024-05-01T14:08:29Z | 60 | blank | +818012345678 | CT1010 | Tokyo | Tokyo | Japan | smartphone | postpaid | 35 |
| SUB0011 | outgoing | blank | true | unknown | EVT10011 | sms | 2024-05-01T15:03:48Z | blank | 2 | +61412345678 | CT1011 | Melbourne | VIC | Australia | tablet | family | 60 |
| SUB0012 | incoming | 4096.8 | false | female | EVT10012 | data | 2024-05-01T16:20:22Z | 3600 | blank | blank | CT1012 | Delhi | DL | India | tablet | postpaid | 22 |
| SUB0013 | incoming | blank | false | male | EVT10013 | call | 2024-05-01T17:14:42Z | 350 | blank | +14165550123 | CT1013 | Vancouver | BC | Canada | smartphone | prepaid | 50 |
| SUB0014 | outgoing | 62.3 | false | female | EVT10014 | data | 2024-05-01T18:38:57Z | 180 | blank | blank | CT1014 | Barcelona | CAT | Spain | feature phone | postpaid | 27 |
| SUB0015 | incoming | blank | false | female | EVT10015 | sms | 2024-05-01T19:00:14Z | blank | 15 | +390612345678 | CT1015 | Rome | Lazio | Italy | smartphone | family | 33 |
| SUB0016 | outgoing | blank | false | male | EVT10016 | call | 2024-05-01T20:09:21Z | 65 | blank | +8613912345678 | CT1016 | Beijing | BJ | China | smartphone | postpaid | 58 |
| SUB0017 | incoming | 20 | false | male | EVT10017 | data | 2024-05-01T21:14:33Z | 360 | blank | blank | CT1017 | Madrid | Madrid | Spain | tablet | prepaid | 44 |
| SUB0018 | outgoing | blank | true | other | EVT10018 | sms | 2024-05-01T21:45:30Z | blank | 8 | +74951234567 | CT1018 | Moscow | MOW | Russia | feature phone | family | 62 |
| SUB0019 | incoming | blank | false | female | EVT10019 | call | 2024-05-01T22:05:00Z | 900 | blank | +5511987654321 | CT1019 | Rio de Janeiro | RJ | Brazil | smartphone | prepaid | 38 |
| SUB0020 | outgoing | 80.2 | false | male | EVT10020 | data | 2024-05-01T23:29:40Z | 600 | blank | blank | CT1020 | New York | NY | USA | smartphone | postpaid | 29 |
What the 200 rows show
from the 200-row sample- 24%is_
roaming = true - 560.6median data_
volume_ mb - 3event types
- 3device types
- 3plan types
- 41location countries
Median 560.6, from 8.2 to 10,240.
- string 12
- integer 3
- float 1
- datetime 1
- boolean 1
Columns
18 columns in four groups| column | type | description | example |
|---|---|---|---|
| Text 12 columns | |||
subscriber_id | string | Unique identifier for each telecom subscriberunique | SUB0001 |
event_id | string | Unique identifier for each usage event (call, SMS, data session)unique | EVT10001 |
event_type | string | Type of usage event: call, sms, or datacall · sms · data | call |
direction | string | Direction of the event: incoming or outgoingincoming · outgoing | outgoing |
counterparty_number | string | Phone number of the other party involved in the event (call/SMS)optional | +12045550121 |
cell_tower_id | string | Identifier for the cell tower used during the eventoptional | CT1001 |
location_city | string | City where the event occurredoptional | San Francisco |
location_state | string | State or region where the event occurredoptional | CA |
location_country | string | Country where the event occurredoptional | USA |
device_type | string | Type of device used for the event (e.g., smartphone, feature phone, tablet)3 types · optional | smartphone |
plan_type | string | Subscriber's telecom plan type (e.g., prepaid, postpaid, family)3 types · optional | postpaid |
subscriber_gender | string | Gender of the subscribermale · female · other · unknown · optional | female |
| Numbers 4 columns | |||
duration_seconds | integer | Duration of the event in seconds (applies to calls and data sessions)0 or more · optional | 120 |
data_volume_mb | float | Volume of data used in megabytes (applies to data sessions)0 or more · optional | 120.5 |
sms_count | integer | Number of SMS messages sent in this event (applies to SMS events)1 or more · optional | 3 |
subscriber_age | integer | Age of the subscriber at the time of the event0 to 120 · optional | 28 |
| Dates and times 1 column | |||
event_datetime | datetime | Timestamp when the event occurred | 2024-05-01T08:15:23Z |
| True or false 1 column | |||
is_roaming | boolean | Indicates if the event occurred while the subscriber was roamingoptional | false |
Use it for
A telecommunications dashboard
The is_
roaming rate, data_ volume_ mb by direction and a breakdown of subscriber_ gender. Excel, Power BI or Tableau. Why do 47 of 200 rows have is_
roaming = true? A class exercise
Hand out the rows and one question. Everyone works from the same 200 rows.
- Subscribers200SUB0001outgoingSUB0003120.5outgoingSUB0009incoming
A software demo
Believable subscribers with event_
id, event_ type and event_ datetime to fill a screen in front of a buyer.
blueprint · telecom-subscriber-usage-patterns
Behind this dataset
Same schema. As many rows as you need.
These 200 rows came out of a blueprint — 18 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.
- Subscriber ID anonymized per record
- Call, SMS, and data usage events tracked
- Device type and plan tier logged
- Location region at event time provided
- Churn propensity calculated monthly
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-subscriber-usage-patterns