Channel
@littlebbydoll
On this record: Topic · Previous handles · Growth · Engagement · What this channel posts · Reactions · Stars · Posts · Citations · Cite this entry
330subscribers
+282 since we began measuring on 1 September 2026
Risers and fallers across the register · movement among entries of Under 1,000.
| Telegram ID | -1003980833107 |
|---|---|
| Type | Channel |
| Username | @littlebbydoll |
| Description | exclusively for the bitches with a pretty soul 𓏲ּ𝄢 реклама и прайс — @dollsdiaryPR 𓏲ּ𝄢 связаться со мной — @dollsanonnbot (либо в лс канала) 𓏲ּ𝄢 буст — https://t.me/boost/littlebbydoll |
| Created | Between 1 April 2026 and 29 August 2026 — estimated from Telegram’s id allocation, not measured. How this range is calculated. |
| First recorded | 1 September 2026 |
| Last confirmed live | 10 November 2026 |
| Measurements held | 6 |
| On Telegram | t.me/littlebbydoll |
Personal blog — a classification, not a measurement. An on-box language model (Qwen3.6-35B-A3B-FP8, prompt version 1) read this channel’s own recent posts on 26 September 2026 and assigned it the closest of 31 fixed categories, at 80% confidence. This is a model’s judgement about what the channel is likely to be about, not a fact this register measured the way a subscriber count or a view count is measured — it can be revised on a later pass, and it carries no weight anywhere else on this page. How this classification works, and the other topics.
@littlebbydoll was previously reachable at this handle, before switching to its current one. This says nothing about who or what answers at the old handle today — only that this channel no longer does.
| Measured (UTC) | Subscribers | Change |
|---|---|---|
| 10 Nov 2026, 09:22 | 330 | no change |
| 10 Nov 2026, 08:47 | 330 | +207 |
| 18 Sept 2026, 13:57 | 123 | +31 |
| 11 Sept 2026, 05:58 | 92 | +44 |
| 1 Sept 2026, 17:15 | 48 | no change |
| 1 Sept 2026, 17:00 | 48 | first reading |
40 posts held, back to 29 August 2026 — the reader has not yet reached the start of this channel’s public history, so older posts may sit further back, unread. Read across 2 pages of Telegram’s post history, 20 posts per page.
ERR is average views per post over the last 30 days divided by subscribers, the definition TGStat uses, so this figure is comparable with the one you will see elsewhere. It falls structurally as a channel grows: a high ERR on a small channel and a low one on a large channel describe reach mathematics, not quality. We publish the figure and the sample it came from and pass no verdict on it.
ER is defined industry-wide as (forwards + reactions + comments) ÷ views — note the denominator is views, not subscribers. Telegram’s public web preview carries views and reactions but not forward or comment counts, so the reaction rate above is the reactions term only and is therefore a floor: the true ER for this channel is higher by an amount we have not measured and will not estimate. It is computed over the 13 of 19 measured posts that carry a reaction reading, and over those same posts' views.
| Window | Rolling 30 days · latest post in window 9 November 2026 |
|---|---|
| Posts held | 40 (29 August 2026 – 9 November 2026) |
| Views total | 8,184 |
| Reactions total | 595 |
| Forwards / comments | not exposed by the public surface — not measured, not estimated |
| Readings taken | 10 Nov 2026, 09:22 UTC |
Views are a single reading per post, taken at the time above. A post published in the last day or two is still accumulating views, which pulls the 30-day average down slightly. That is a property of the standard definition rather than a fault in it, so we keep the definition rather than “correcting” the number into something nobody can reproduce.
Precision. Telegram publishes view counts on its public widget in short form — 8.12K, 3.7M — so any reading at or above 1,000 reaches us rounded to three significant figures, and only counts below 1,000 are exact. Averages and rates derived from them are shown to the same precision rather than to the unit: a figure like 3,701,250 would assert digits nobody measured.
Reaction counts are published per emoji and rounded the same way, so a total below 1,000 is exact and a larger one is a sum that may carry a rounded component from each emoji above 1,000. Because it is a sum, it does not look rounded — read a large reaction total as three significant figures per contributing emoji rather than as the figure it prints.
Lifetime counters from Telegram’s own channel header, read 10 November 2026 — not the date at the top of this page, which is when the subscriber count was last read. Below Telegram’s rounding threshold, so these counts are exact.
Measured directly from 1 video with a duration reading, out of the posts we hold for this channel — not this channel’s whole posting history, only the sample this register has actually read. An exact reading to the second, taken from the post itself rather than from Telegram’s own rounded chrome, so it carries no ≈ mark.
761 reactions across 26 posts, in 12 distinct kinds. The most used accounts for 17.1% of them.
| Reaction | Count | Share | Share, drawn |
|---|---|---|---|
| custom 5246981942875821647 | 130 | 17.1% | |
| custom 5420567087707864895 | 128 | 16.8% | |
| custom 5233651631404385374 | 125 | 16.4% | |
| custom 5400268805979005327 | 97 | 12.7% | |
| custom 5420365735346061680 | 85 | 11.2% | |
| custom 5422472807646772159 | 72 | 9.46% | |
| custom 5294000654967153192 | 29 | 3.81% | |
| custom 5422679721991221911 | 22 | 2.89% | |
| custom 5285051566619899910 | 21 | 2.76% | |
| custom 5397682209169629313 | 21 | 2.76% | |
| custom 5395685049376982911 | 19 | 2.50% | |
| custom 5195118683768247577 | 12 | 1.58% |
Custom emoji. Every row above is a Telegram custom emoji, which the public preview renders as an element carrying only a numeric id — no character, and no image we can reach. The id is printed as-is rather than substituted with a look-alike glyph, because a stand-in would be our invention showing where a measurement should be. The counts beside them are Telegram’s.
No sentiment is inferred, and none should be read in. This table is ordered by count and by nothing else. Emoji do not carry stable meaning across languages or communities — 🙏 is thanks in one channel and mourning in another — so we publish which ones were pressed and how often, and pass no judgement on what an audience meant by them.
Precision. Telegram publishes reaction counts per emoji and short-forms each one — 4.34K, 1.2M — so any single kind at or above 1,000 reaches us at three significant figures, and only counts below 1,000 are exact. The shares above are ratios of those figures and carry the same error. This is also why the total here can differ slightly from a reaction total printed elsewhere on the page: both are sums of the same rounded parts, taken over samples with different edges.
Coverage. Reactions were read on 26 of the 40 sampled posts in this sample. Summed by Telegram’s own count on each post — not by adding up the per-emoji breakdown above — those same posts carry 761 reactions in total: the kind of figure the paragraph above means by “a reaction total printed elsewhere on the page”.
Measured over the 40 most recent posts we hold, published 29 August 2026 to 9 November 2026, using the newest reading held for each. Telegram Stars are excluded: they are a payment, not a reaction, and they have their own section.
A paid reaction is a reader spending Telegram Stars — bought with money — on a post by @littlebbydoll. Telegram publishes the count on the public post preview alongside ordinary reactions, and this register reads it there. It is the only figure on this site that measures money moving rather than attention.
Stars are not reactions, and the two are never added. They are rendered in the same strip on Telegram and counted in the same shape, but one is a tap and the other is a purchase. The reaction totals and the engagement rate elsewhere on this page exclude every figure in this section, and no rate here is computed against a reaction count.
This is not revenue, and we publish no currency figure. What a Star costs a reader and what it pays a channel are different numbers, Telegram takes a share we cannot observe, and the terms have changed. Converting a Star count into money would be an estimate dressed as a measurement, so the count is where we stop.
Counted over the 40 most recent posts we hold for this entry, published 29 August 2026 to 9 November 2026. Star counts above 1,000 reach us in Telegram’s short form and carry the same three-significant-figure rounding as everything else on this page.
Telegram’s own ‘edited’ marker: 1 of 20 posts held from the last 30 days (5.00%) carried it when this register last read them. The marker says a post was changed after publishing, not what it said before — this register holds the earlier wording only where an edit fell between two of its own reads (see the edit ledger and how it is measured).
первый отзыв, причем очень хороший! напоминаю, что осталось еще 1 место среди 3-х покупателей, которые получат скидку при покупке рекламы 🩷
custom 54203657353460616807custom 52469819428758216475custom 54224728076467721595custom 52336516314043853742custom 54002688059790053272custom 54205670877078648951
🫥🫥 🫥 мой кинн на эту (уже заканчивающуюся) осень
custom 542247280764677215918custom 52336516314043853748custom 52469819428758216478custom 54002688059790053274custom 54203657353460616803custom 54205670877078648951
Sticker, posted without a caption
custom 52336516314043853741custom 52469819428758216471custom 54224728076467721591
в последнее время замечаю, то что актив сильно упал + пошли дикие отписки (~15 человек за неделю). также часто отписываются после взаимных пиаров/рекламы или подгонов к рекламе(( ребят, i’m doing my best и реклама — не причина для отписок, так что надеюсь на поддержку, понимание и фидбэк всех люблю 🤍
custom 523365163140438537420custom 54205670877078648959custom 54224728076467721594custom 54203657353460616802custom 52469819428758216471custom 54002688059790053271
Posted without readable text
custom 542036573534606168020custom 523365163140438537413custom 524698194287582164712custom 54224728076467721593custom 54002688059790053272custom 54205670877078648952
Sticker, posted without a caption
Photo, posted without a caption
custom 523365163140438537439custom 540026880597900532727custom 542036573534606168014custom 54205670877078648954custom 54224728076467721591
Sticker, posted without a caption
🔤 так, раз нас стало больше, с сегодняшнего дня в канале продается реклама (причем очень дешевая!!) также первым 3 покупателям действует скидка: • тариф babydoll — 250р 150р • тариф 1 — 150р 100р прайс и вся информация по поводу рекламы — @dollsdiarypr 💫👄 UPD: осталось еще 1 место для скидки
custom 542247280764677215915custom 52336516314043853749custom 52469819428758216478
You know my clothes still smell like you All my photographs say that we’re still young I pretend I’m not hurt And go about the world like I’m having fun
custom 524698194287582164724custom 523365163140438537414custom 542056708770786489513custom 54002688059790053274custom 54203657353460616803custom 54224728076467721593
Sticker, posted without a caption
😀😀happy Halloween!!! 🧡
custom 542056708770786489530custom 523365163140438537410custom 54224728076467721598custom 54002688059790053273
Showing the 12 most recent of 40 posts we hold for @littlebbydoll. View and reaction counts are the latest single reading for each post, not a live figure, and a recent post is still accumulating both. A view count marked ≈ was rounded by Telegram before we ever saw it — t.me prints views in full below 1,000 and to three significant figures above, so ≈1,200,000 means somewhere between 1,150,000 and 1,249,999. Unmarked counts are exact. Text is reproduced from the public post preview and truncated for length.
Stars beside a post are paid reactions — Telegram Stars, bought with money and spent on that post. They are a different unit from reactions and are never added to them, here or anywhere else on this page.
Republished by
Channels on the register that have forwarded this channel's posts into their own feed.
Built only from forwarded posts we have actually read, on both sides. Coverage is early and deliberately incomplete: a missing link means we have not read the post that would prove it, never that the relationship does not exist. Counts are distinct forwarded posts observed, so they only ever go up as we read more.
Named by 2 registered channels — every channel on the register whose own posts have named this one, by its current username or any other username it currently holds, merged from two separately captured readings of the same fact so a namer caught by only one of them is not missed and a namer both caught is not counted twice. A username this channel has since dropped is not matched — that handle may belong to someone else now, and crediting today’s namer to yesterday’s owner would misattribute it.
Named by
Channels on the register whose posts name this channel's handle.
Names
Channels on the register whose handles appear in this channel's posts.
A mention is a weaker signal than a forward and is counted separately for that reason — naming a channel is not republishing it, and a handle in a post body is easy to place deliberately. The post counts beside each row below are distinct posts in which the handle appeared, from posts we have read on both sides — the “Named by N registered channels” figure above is a different count, of distinct NAMING CHANNELS rather than posts, and is not the sum of the rows under it.
A live page changes as we take new readings, so a citation should name the measurement it is based on, not just the URL. The line below cites the subscriber count as measured 10 November 2026 — this entry's latest reading, not the date you are reading this.
“doll’s diary” (@littlebbydoll), 330 subscribers as measured 10 November 2026. Telegram Register, tgregister.com/channel/littlebbydoll.
Full measurement history, CC BY 4.0. Every reading this register holds for this entry, not just the latest one, as a dated, downloadable record: CSV · JSON. Free to use with attribution to tgregister.com. Each file carries its own generation timestamp, which is the figure to cite for exactly when the data was retrieved.