Telegram RegisterThe public register of Telegram
Telegram profile photo for 上班划水之无聊图

Channel

上班划水之无聊图

@goworkbitch

On this record: Topic · Growth · Engagement · What this channel posts · Reactions · Posts · Posts recorded as deleted · Citations · Telegram's recommendations · Cite this entry

25,325subscribers

+648 since we began measuring on 6 August 2026

Risers and fallers across the register · movement among entries of 10,000–31,623.

Register entry

Telegram ID-1001174703316
TypeChannel
Username@goworkbitch
Description活干完了吗?还在玩手机! 注意:本频道讨论群仅用作评论区,不接受任何人加群,尝试加群会立刻被踢。若误点加入被踢且无法访问评论区,需稍等一会儿即自动解封。 另外,本频道主只有一个人,所以请避免不和谐讨论,如果将来实在无暇管理可能会关闭评论区。
Created7 July 2018 — measured — cross-checked against a third-party dataset (ext.tg_channel)
First recorded6 August 2026
Last confirmed live12 November 2026
Measurements held64
Confirmed unchanged1 time, most recently 12 November 2026
On Telegramt.me/goworkbitch

Topic

Memes & entertainment — a classification, not a measurement. An on-box language model (Qwen3.6-35B-A3B-UD-Q6_K_XL, prompt version 1) read this channel’s own recent posts on 20 August 2026 and assigned it the closest of 31 fixed categories, at 90% 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.

Growth

24,67725,32525,0016 August 202612 November 2026
64 measurements spanning 98 days, net +648. 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 24,580–25,422 and does not start at zero.
Measurement log — every subscribers count we have recorded, most recent 20 of 64
Measured (UTC)SubscribersChange
12 Nov 2026, 13:0625,325+33
10 Nov 2026, 08:3925,292+34
8 Nov 2026, 21:1525,258+14
7 Nov 2026, 11:4725,244+5
6 Nov 2026, 08:5925,239+8
5 Nov 2026, 10:5625,231+14
4 Nov 2026, 08:4425,217+11
3 Nov 2026, 10:4025,206+9
2 Nov 2026, 07:1125,197+6
1 Nov 2026, 10:2625,191+10
31 Oct 2026, 09:0525,181+9
30 Oct 2026, 11:1025,172+3
29 Oct 2026, 08:1525,169+13
28 Oct 2026, 07:2725,156+5
27 Oct 2026, 09:3525,151+9
26 Oct 2026, 09:3525,142+2
25 Oct 2026, 12:5525,140+3
24 Oct 2026, 15:5825,137+3
22 Oct 2026, 15:5525,134+6
21 Oct 2026, 09:0125,128first reading

Engagement

456 posts held, back to 3 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 144 pages of Telegram’s post history, 20 posts per page.

ERR · 30 days
4.75%
avg views ÷ 25,325 subscribers
Avg views / post
1,200
122 posts measured
Reaction rate
0.75%
reactions ÷ views · ER floor
Posts in window
122
of 456 held

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 119 of 122 measured posts that carry a reaction reading, and over those same posts' views.

What these figures were computed from
WindowRolling 30 days · latest post in window 12 November 2026
Posts held456 (3 August 2026 – 12 November 2026)
Views total146,805
Reactions total1,097
Forwards / commentsnot exposed by the public surface — not measured, not estimated
Readings taken12 Nov 2026, 21:55 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.

What this channel posts

Photos
≈4,970
Videos
≈8,920
Links
≈58

Lifetime counters from Telegram’s own channel header, read 12 November 2026 — not the date at the top of this page, which is when the subscriber count was last read. A count marked ≈ was rounded by Telegram before we ever saw it — t.me prints these counters in full below 1,000 and to three significant figures above, so ≈142,000 means somewhere between 141,500 and 142,499.

Video runtime
3h 14m
Average length
27s

Measured directly from 433 videos 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.

Reaction mix

3,838 reactions across 434 posts, in 42 distinct kinds. The most used accounts for 12.7% of them.

Every reaction kind recorded on the sample, most used first
ReactionCountShareShare, drawn
😁48612.7%
❤3469.02%
🆒2426.31%
🥰2145.58%
😱2015.24%
🤣1975.13%
💩1925.00%
🔥1854.82%
👍1834.77%
😨1574.09%
💯1413.67%
🤯1313.41%
🤔1173.05%
🌚1012.63%
🤪1012.63%
👏862.24%
🍌842.19%
😭782.03%
🌭631.64%
🤮541.41%
22 further kinds47912.5%

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 441 of the 456 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 3,905 reactions in total: the kind of figure the paragraph above means by “a reaction total printed elsewhere on the page”.

Measured over the 456 most recent posts we hold, published 3 August 2026 to 12 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.

Recent posts

Telegram’s own ‘edited’ marker: 1 of 122 posts held from the last 30 days (0.82%) 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).

11 Nov 2026, 11:27 UTC923 views20 reactionsread 12 November 2026
Video

Video, posted without a caption

😭19😨1

11 Nov 2026, 11:11 UTC887 views13 reactionsread 12 November 2026
Video

乌鸦:我从火里给你抢回来的你又不要

🔥10🥰3

11 Nov 2026, 02:23 UTC≈1,020 views5 reactionsread 12 November 2026
Video

Video, posted without a caption

🔥4😨1

Showing the 12 most recent of 456 posts we hold for @goworkbitch. 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.

Posts recorded as deleted after publishing

We recorded 2 posts on @goworkbitch as deleted — posts this register held that were missing from the channel’s public page on two separate reads, taken from different network addresses at least an hour apart.

A deletion is not wrongdoing. This register can see that a post it held is no longer on the channel’s public page, and when — not why. Expired ad placements, reposts, rotating links and corrections all look the same. This is a count of recorded detections, not an exact total: it misses deletions we could not see, because only a post we held and later re-read inside the page can be seen to go, and it may include a small number of wrong records. How this is measured.

First seen missing
12 August 2026
Most recent seen missing
23 August 2026
Median time before seen missing
40 hours
Seen missing in the last 30 days
0

Forward network

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.

Mentions

Named by 3 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.

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.

Channels Telegram recommends alongside this one

Telegram’s own answer, not this register’s. When this register asks Telegram’s API what is similar to this channel, this is the list it returns, in the exact order Telegram returns it — never re-sorted by subscribers or by anything else this register measures. The relationship, and the order, are Telegram’s; we record them and date them, and make no claim of our own about which of these channels actually resemble this one.

某科学的一个频道
@titan_pain · 20,849
#1
煎蛋无聊图
@jandan_pic · 25,561
#2
Foolish TraceWind
@FoolishTraceWind · 16,723
#3
在花🎗️科技圈
@zaihuapd · 290,142
#4
〄FW
@JISFW · 12,885
#5
每日消费电子观察
@CE_Observe · 77,679
#6
风向旗参考快讯
@xhqcankao · 200,273
#7
平壤卫视
@pingrangTV · 29,366
#8
竹新社
@tnews365 · 167,192
#9
Solidot
@solidot · 48,811
#10
每日无数猫
@miaowu · 19,925
#11
简中互联网废物大赏
@fucku_idiot · 41,850
#12
灵车漂移
@Hearse_Drifting · 10,901
#13
沙雕微博收集
@funnyweibo · 4,847
#14
Newlearnerの自留地
@NewlearnerChannel · 68,297
#15
LiFePO4:沙雕吐槽
@lifepofour · 2,209
#16
蛋挞观察室
@ijustseesee · 2,969
#17
TG吃瓜黑料八卦
@baguabox · 33,146
#18
( ゚∀。) Official
@WjwOfficial · 6,246
#19
层叠 - The Cascading
@outvivid · 9,324
#20
VPS信号旗播报
@vps_xhq · 50,835
#21
今日份的豆酱
@today_bean · 2,948
#22
贪玩电动(停售实体版)
@oojbk · 2,212
#23
LoopDNS资讯播报
@DNSPODT · 73,288
#24
cnBeta.COM中文业界资讯站 - 总频道(精选新闻)
@cnbeta_com · 27,396
#25
蓝点网订阅频道
@landiansub · 47,142
#26
zrj766的频道
@zrj96 · 17,853
#27
每日高保真神论
@wtfhifi · 2,019
#28
Milkice's 生而喵喵
@milkice_portal · 3,393
#29
大头打飞机
@BigXhead_Aeroplane · 1,957
#30
今天abc看了啥🤔
@abcthoughts · 7,136
#31
Yummy 😋
@GodlyNews1 · 71,235
#32
即刻精选
@jike_collection · 35,913
#33
NFW
@NewsFW · 6,818
#34
少数派sspai
@sspai · 39,123
#35
DBin_K 🤯 Tingle 灵光一闪 💡
@DBinKBB · 2,345
#36
柠檬的日常搞怪生活
@ilemonrain_channel · 2,744
#37
拳殖猎人🐺
@colonized_people · 2,180
#38
NS新闻转报
@SwitchNewCN · 7,432
#39
Android Weekly Update ⚡️
@update4weekly · 5,238
#40
2.5次元日常 🍉
@acgdaily · 17,329
#41
车速过快🚦开车娱乐搞笑沙雕
@chesgk · 5,058
#42
瞎玩菌 #SFW
@blindgamer · 10,785
#43
音游沙雕频道
@yingyoushadiao · 3,435
#44
每天趣事
@meitian · 28,500
#45
笔记本:Lin's 文字世界 : 个人见闻/B站视频/网络见闻
@LinsBookA · 8,090
#46
可爱小狗
@keaixiaogou · 2,522
#47
LetITFly News
@LetITFlyW · 9,732
#48
灵车漂移 ~ 波音 ver. ~
@tesla_drifting · 1,507
#49
Karen医生の日常
@KarenMoeMoe · 9,352
#50
迷因備份區(偶爾有貓)
@memes_backup · 2,870
#51
Programmer Jokes
@programmerjokes · 105,971
#52

Read from Telegram’s recommendation API, most recently 15 September 2026. Telegram holds a list like this for a small and growing share of the register — how this is measured, and why most channel pages show nothing here.

Appears in Telegram’s recommendations for other channels

The reverse of the list above, and a different kind of signal. This does not require this channel to have ever been asked about directly — each row below is a channel we DID ask Telegram about, whose Telegram-generated list happened to include this one. A channel can appear here with an empty list above it, because being named by someone else’s query is independent of having been queried itself.

如何与沙雕相处
@ruheyushadiaoxiangchu · 28,376
Telegram ranks this channel #1 of 44 here — alongside 43 others — read 9 September 2026
每天趣事
@meitian · 28,500
Telegram ranks this channel #6 of 20 here — alongside 19 others — read 9 September 2026
煎蛋无聊图
@jandan_pic · 25,561
Telegram ranks this channel #8 of 51 here — alongside 50 others — read 14 September 2026
平壤卫视
@pingrangTV · 29,366
Telegram ranks this channel #11 of 45 here — alongside 44 others — read 8 September 2026
每日无数猫
@miaowu · 19,925
Telegram ranks this channel #18 of 55 here — alongside 54 others — read 29 September 2026
TG吃瓜黑料八卦
@baguabox · 33,146
Telegram ranks this channel #30 of 38 here — alongside 37 others — read 4 September 2026
2019-nCoV疫情实时播报🅥
@nCoV2019 · 32,428
Telegram ranks this channel #35 of 59 here — alongside 58 others — read 4 September 2026
即刻精选
@jike_collection · 35,913
Telegram ranks this channel #42 of 48 here — alongside 47 others — read 2 September 2026
简中互联网废物大赏
@fucku_idiot · 41,850
Telegram ranks this channel #44 of 47 here — alongside 46 others — read 30 August 2026
cnBeta.COM中文业界资讯站 - 总频道(精选新闻)
@cnbeta_com · 27,396
Telegram ranks this channel #55 of 55 here — alongside 54 others — read 10 September 2026
每日消费电子观察
@CE_Observe · 77,679
Telegram ranks this channel #59 of 62 here — alongside 61 others — read 19 August 2026

This channel appears in 11 seed channels' Telegram-generated recommendation lists in total. Each is Telegram’s list for THAT channel, not this one — see how this is measured.

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

“上班划水之无聊图” (@goworkbitch), 25,325 subscribers as measured 12 November 2026. Telegram Register, tgregister.com/channel/goworkbitch.

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.