Channel
@daite_lapshi_babes
On this record: Topic · Growth · Engagement · Reactions · Posts · Citations · Cite this entry
555subscribers
-13 since we began measuring on 7 August 2026
Risers and fallers across the register · movement among entries of Under 1,000.
| Telegram ID | -1001901912399 |
|---|---|
| Type | Channel |
| Username | @daite_lapshi_babes |
| Created | Between 1 March 2023 and 31 January 2024 — estimated from Telegram’s id allocation, not measured. How this range is calculated. |
| First recorded | 7 August 2026 |
| Last confirmed live | 13 September 2026 |
| Measurements held | 7 |
| Confirmed unchanged | 1 time, most recently 13 September 2026 |
| On Telegram | t.me/daite_lapshi_babes |
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 21 September 2026 and assigned it the closest of 31 fixed categories, at 72% 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 why it has no browse page of its own yet.
| Measured (UTC) | Subscribers | Change |
|---|---|---|
| 13 Sept 2026, 02:37 | 555 | -1 |
| 5 Sept 2026, 16:16 | 556 | -3 |
| 28 Aug 2026, 22:03 | 559 | -1 |
| 22 Aug 2026, 22:04 | 560 | -2 |
| 14 Aug 2026, 14:25 | 562 | -5 |
| 7 Aug 2026, 17:14 | 567 | -1 |
| 7 Aug 2026, 10:18 | 568 | first reading |
6 posts held, back to 5 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 1 page of Telegram’s post history, 20 posts per page.
Nothing published in the last 30 days. ERR and ER are rolling 30-day measures, so there is nothing to compute — we hold 6 posts for this entry, the most recent from 7 August 2026. An engagement rate over an empty window would be a number about nothing.
78 reactions across 6 posts, in 3 distinct kinds. The most used accounts for 43.6% of them.
| Reaction | Count | Share | Share, drawn |
|---|---|---|---|
| custom 5433749085368625469 | 34 | 43.6% | |
| custom 5395338235062788608 | 24 | 30.8% | |
| custom 5260334802925538525 | 20 | 25.6% |
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 6 of the 6 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 78 reactions in total: the kind of figure the paragraph above means by “a reaction total printed elsewhere on the page”.
Measured over the 6 most recent posts we hold, published 5 August 2026 to 7 August 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.
🍔🍔 как это началось/как это закончилось Но хэй, зато на свой первый месяц в Китае я заработала сама, наверное, это считается за что-то.. Только что продала однокласснице алёнку за 5 юаней, я обязательно выживу🙏
custom 53953382350627886083custom 52603348029255385252custom 54337490853686254692
🙏🙏 учитель перед экзаменом сказал, что баллов 70 всё равно все получат, и что за списывание отрубят руки, я не понимаю, насколько серьёзно относиться к этому учебному заведению 💓 Ещё есть отвратительная фотка рекомендаций из лоусона: суперское что-то с орео и апельсиновый сок, который на вкус как апельсиновый сок! Без химозного привкуса!
custom 54337490853686254699custom 53953382350627886085custom 52603348029255385254
💓🍜 Сегодня кондиционеры не работали почти нигде💇 🍜 Это невозможно... Где-то полчаса последней пары мы с подружкой просто галлюцинировали, я думаю~ сегодня потратила все свои деньги лол теперь буду 脱贫🙏 🍔 хожу на все мастер-классы, потому что сувениры покупать не на что, я просто выберу 4-5 людей, которым раздам свои поделки, и вообще, кто хочет подарок, пусть кинет денег😒 💓 А ещё китайская цензура запретила мне пет…
custom 52603348029255385256custom 54337490853686254696custom 53953382350627886084
🍔🍔 нужно какое-то название для этого явления, когда я ставлю себя в ПАТОВЫЕ ситуации У меня таких приколов полный рюкзак, даже не всякая мелочь, как сегодня Я вам как-нибудь расскажу, за что меня уволили, и почему я не поехала в Китай на год раньше, хотя могла :D Но сперва сделаю какой-нибудь умный пост, а то вы усомнитесь, как такой человек вообще дожил до своих лет и ещё людей учит, и будет много отписок🫶
custom 54337490853686254695custom 53953382350627886084custom 52603348029255385253
🍔🍔 МЕСТА, В КОТОРЫХ Я ОКАЗАЛАСЬ, ПОКА ИСКАЛА ПОСТАМАТ??? "Ещё чуть-чуть, и я найду страну чудес, но не свою фигурку по магичке" — думала я, агрессивно фотографируя чудеса природы
custom 54337490853686254695custom 53953382350627886084custom 52603348029255385252
💓🍜 забрала утырка на таобао и книжку~ Присаживайтесь — я опять сделала что-то слегка не так 🍔 Прямо напротив входа в наше общежитие есть постамат, очень удобно!.. конечно, я заказала не туда)))) Я заказала в постамат у школы. Ничего страшного, прогуляюсь... и так я прогулялась больше часа, обошла всю территорию кампуса, нашла ЖИВОТНЫХ И ЛОТОСЫ, НО НЕ ТХАМАДЕ ПОСТАМАТ 🍜 Потом я ещё не понимала, как сканировать и …
custom 54337490853686254697custom 53953382350627886084custom 52603348029255385253
Showing the 6 most recent of 6 posts we hold for @daite_lapshi_babes. 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.
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.
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 13 September 2026 — this entry's latest reading, not the date you are reading this.
“Дайте Лапши! 🍜 китайский и всякое” (@daite_lapshi_babes), 555 subscribers as measured 13 September 2026. Telegram Register, tgregister.com/channel/daite_lapshi_babes.
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.