Telegram RegisterThe public register of Telegram
Telegram profile photo for 小涛日记

Channel

小涛日记

@baovc4

On this record: Growth · Engagement · What this channel posts · Posts · Handles named that no longer answer · Cite this entry

84subscribers

-2 since we began measuring on 7 August 2026

Risers and fallers across the register · movement among entries of Under 1,000.

Register entry

Telegram ID-1003124714645
TypeChannel
Username@baovc4
CreatedBetween 1 September 2025 and 30 November 2025— estimated from Telegram’s id allocation, not measured. How this range is calculated.
First recorded9 August 2026
Last confirmed live31 August 2026
Measurements held4
Confirmed unchanged2 times, most recently 31 August 2026
On Telegramt.me/baovc4

Growth

8486857 August 2026 — 86 subscribers8 August 2026 — 85 subscribers9 August 2026 — 85 subscribers24 August 2026 — 84 subscribers7 August 202624 August 2026
4 measurements spanning 17 days, net -2. Dots are measurements; the straight line between them is drawn to join them, not to claim we know the path taken in between — snapshots are recorded only when a count changes, so gaps mean “no change observed”, never “interpolated”. The vertical axis spans 84–86 and does not start at zero.
Measurement log — every subscribers count we have recorded
Measured (UTC)SubscribersChange
24 Aug 2026, 23:4484-1
9 Aug 2026, 17:0185no change
8 Aug 2026, 08:3685-1
7 Aug 2026, 18:4886first reading

Engagement

6 posts held, back to 23 April 2026the reader has not yet reached the start of this channel’s public history, so older posts may sit further back, unread. Read across 1 pageof 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 30 June 2026. An engagement rate over an empty window would be a number about nothing.

What this channel posts

Video runtime
38s
Average length
38s

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.

Recent posts

30 Jun 2026, 08:57 UTC152 viewsread 9 August 2026
Photo

以后先不给钱的 不要来找我 问要个钱磨磨唧唧的 要不就跑路 还jb骂我

19 May 2026, 19:49 UTC279 viewsread 9 August 2026

bb娱乐黑台子 大家不要玩 小号从来没赢过 大号也不知输多少钱了 每次代打电话赚到钱都会支持bb 没想到每次都让我失望 赌博害人 害人害己 劝大家早日戒赌 早日上岸

13 May 2026, 17:48 UTC276 viewsread 9 August 2026

人咋活的那么累呀 上个厕所也要被爸妈说 大半夜吵他们睡觉 好想哭

28 Apr 2026, 13:25 UTC310 viewsread 9 August 2026
Photo

@TYLW88888 莫言国际 太阳合作了几天时间,偶尔扫码几百1000. 慢慢的就让我给他欠账 26号那天让我转5000没给 非要1000人名币 给他转了就不回信息 踢我出群 下我管理 禁言 这样的人1000人名币都黑谁还敢给他送人呢

23 Apr 2026, 18:35 UTC523 viewsread 9 August 2026

认识一年多了 第一次找她举牌 20u 直接给我跑了 畜生茶茶 骗子ID: @cds207 @mensini

Showing the 6 most recent of 6 posts we hold for @baovc4. 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.

Cite this entry

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 24 August 2026 — this entry's latest reading, not the date you are reading this.

“小涛日记” (@baovc4), 84 subscribers as measured 24 August 2026. Telegram Register, tgregister.com/channel/baovc4.

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.