Telegram RegisterThe public register of Telegram
Telegram profile photo for 济南青岛公开资源(认证)

Channel

济南青岛公开资源(认证)

@sosuokV

On this record: Topic · Growth · Engagement · What this channel posts · Reactions · Posts · Posts edited after publishing · Posts recorded as deleted · Citations · Cite this entry

43,827subscribers

+12,070 since we began measuring on 20 August 2026

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

Register entry

Telegram ID-1001914565751
TypeChannel
Username@sosuokV
CreatedBetween 1 April 2023 and 31 October 2023 — estimated from Telegram’s id allocation, not measured. How this range is calculated.
First recorded20 August 2026
Last confirmed live7 November 2026
Measurements held47
Confirmed unchanged1 time, most recently 7 November 2026
On Telegramt.me/sosuokV

Topic

Other / unclassifiable — 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 9 September 2026 and assigned it the closest of 31 fixed categories, at 86% 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

31,75743,82737,79220 August 2026 — 31,757 subscribers21 August 2026 — 31,858 subscribers23 August 2026 — 32,148 subscribers24 August 2026 — 32,325 subscribers26 August 2026 — 32,345 subscribers27 August 2026 — 32,513 subscribers28 August 2026 — 32,665 subscribers29 August 2026 — 32,798 subscribers30 August 2026 — 32,889 subscribers31 August 2026 — 32,952 subscribers1 September 2026 — 33,140 subscribers2 September 2026 — 33,259 subscribers3 September 2026 — 33,363 subscribers5 September 2026 — 33,912 subscribers9 September 2026 — 34,426 subscribers11 September 2026 — 34,560 subscribers13 September 2026 — 34,489 subscribers15 September 2026 — 34,711 subscribers17 September 2026 — 35,086 subscribers24 September 2026 — 36,434 subscribers3 October 2026 — 38,208 subscribers8 October 2026 — 39,102 subscribers12 October 2026 — 40,126 subscribers14 October 2026 — 40,543 subscribers15 October 2026 — 40,673 subscribers16 October 2026 — 40,914 subscribers17 October 2026 — 41,148 subscribers18 October 2026 — 41,383 subscribers19 October 2026 — 41,572 subscribers20 October 2026 — 41,770 subscribers21 October 2026 — 42,026 subscribers22 October 2026 — 42,108 subscribers23 October 2026 — 42,244 subscribers24 October 2026 — 42,300 subscribers25 October 2026 — 42,511 subscribers26 October 2026 — 42,605 subscribers27 October 2026 — 42,753 subscribers28 October 2026 — 42,800 subscribers29 October 2026 — 43,017 subscribers30 October 2026 — 43,026 subscribers1 November 2026 — 43,121 subscribers2 November 2026 — 43,238 subscribers2 November 2026 — 43,429 subscribers4 November 2026 — 43,542 subscribers5 November 2026 — 43,649 subscribers6 November 2026 — 43,728 subscribers7 November 2026 — 43,827 subscribers20 August 20267 November 2026
47 measurements spanning 78 days, net +12,070. 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 29,947–45,638 and does not start at zero.
Measurement log — every subscribers count we have recorded, most recent 20 of 47
Measured (UTC)SubscribersChange
7 Nov 2026, 04:3643,827+99
6 Nov 2026, 03:4143,728+79
5 Nov 2026, 00:3843,649+107
4 Nov 2026, 00:2543,542+113
2 Nov 2026, 21:5943,429+191
2 Nov 2026, 01:0843,238+117
1 Nov 2026, 02:0843,121+95
30 Oct 2026, 22:5643,026+9
29 Oct 2026, 21:0643,017+217
28 Oct 2026, 22:2142,800+47
27 Oct 2026, 19:3742,753+148
26 Oct 2026, 20:4642,605+94
25 Oct 2026, 21:2742,511+211
24 Oct 2026, 19:0842,300+56
23 Oct 2026, 18:4642,244+136
22 Oct 2026, 21:3642,108+82
21 Oct 2026, 15:3542,026+256
20 Oct 2026, 09:2741,770+198
19 Oct 2026, 06:1941,572+189
18 Oct 2026, 06:1741,383first reading

Engagement

102 posts held, back to 23 May 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 140 pages of Telegram’s post history, 20 posts per page.

ERR · 30 days
2.93%
avg views ÷ 43,827 subscribers
Avg views / post
1,280
40 posts measured
Reaction rate
0.043%
reactions ÷ views · ER floor
Posts in window
40
of 102 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 9 of 40 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 6 November 2026
Posts held102 (23 May 2026 – 6 November 2026)
Views total51,360
Reactions total16
Forwards / commentsnot exposed by the public surface — not measured, not estimated
Readings taken7 Nov 2026, 02:00 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

Video runtime
1m 28s
Average length
9s

Measured directly from 10 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

75 reactions across 25 posts, in 8 distinct kinds. The most used accounts for 85.3% of them.

Every reaction kind recorded on the sample, most used first
ReactionCountShareShare, drawn
❤6485.3%
👍34.00%
🎉22.67%
🔥22.67%
❤‍🔥11.33%
🎄11.33%
💋11.33%
🤩11.33%

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 27 of the 102 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 75 reactions in total: the kind of figure the paragraph above means by “a reaction total printed elsewhere on the page”.

Measured over the 102 most recent posts we hold, published 23 May 2026 to 6 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: 3 of 40 posts held from the last 30 days (7.50%) 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).

6 Nov 2026, 11:59 UTC137 views1 reactionsread 7 November 2026

✅西安资源 ✅昆明资源 ✅南昌资源 ✅惠州资源 ✅义乌资源 ✅武汉资源 ✅东北资源 ✅海南资源 ✅天津资源 👨‍👩‍👧‍👦山东群组 🛜其它地区

🎄1

5 Nov 2026, 16:59 UTC77 views1 reactionsread 6 November 2026

✅西安资源 ✅昆明资源 ✅南昌资源 ✅惠州资源 ✅义乌资源 ✅武汉资源 ✅东北资源 ✅海南资源 ✅天津资源 👨‍👩‍👧‍👦山东群组 🛜其它地区

🤩1

4 Nov 2026, 21:59 UTC174 viewsread 5 November 2026

✅西安资源 ✅昆明资源 ✅南昌资源 ✅惠州资源 ✅义乌资源 ✅武汉资源 ✅东北资源 ✅海南资源 ✅天津资源 👨‍👩‍👧‍👦山东群组 🛜其它地区

4 Nov 2026, 02:59 UTC168 viewsread 4 November 2026

✅西安资源 ✅昆明资源 ✅南昌资源 ✅惠州资源 ✅义乌资源 ✅武汉资源 ✅东北资源 ✅海南资源 ✅天津资源 👨‍👩‍👧‍👦山东群组 🛜其它地区

3 Nov 2026, 07:59 UTC209 viewsread 4 November 2026

✅西安资源 ✅昆明资源 ✅南昌资源 ✅惠州资源 ✅义乌资源 ✅武汉资源 ✅东北资源 ✅海南资源 ✅天津资源 👨‍👩‍👧‍👦山东群组 🛜其它地区

2 Nov 2026, 12:59 UTC173 viewsread 3 November 2026

✅西安资源 ✅昆明资源 ✅南昌资源 ✅惠州资源 ✅义乌资源 ✅武汉资源 ✅东北资源 ✅海南资源 ✅天津资源 👨‍👩‍👧‍👦山东群组 🛜其它地区

1 Nov 2026, 17:59 UTC60 viewsread 2 November 2026

✅西安资源 ✅昆明资源 ✅南昌资源 ✅惠州资源 ✅义乌资源 ✅武汉资源 ✅东北资源 ✅海南资源 ✅天津资源 👨‍👩‍👧‍👦山东群组 🛜其它地区

31 Oct 2026, 22:59 UTC155 viewsread 1 November 2026

✅西安资源 ✅昆明资源 ✅南昌资源 ✅惠州资源 ✅义乌资源 ✅武汉资源 ✅东北资源 ✅海南资源 ✅天津资源 👨‍👩‍👧‍👦山东群组 🛜其它地区

31 Oct 2026, 03:59 UTC117 viewsread 31 October 2026

✅西安资源 ✅昆明资源 ✅南昌资源 ✅惠州资源 ✅义乌资源 ✅武汉资源 ✅东北资源 ✅海南资源 ✅天津资源 👨‍👩‍👧‍👦山东群组 🛜其它地区

30 Oct 2026, 08:59 UTC207 viewsread 31 October 2026

✅西安资源 ✅昆明资源 ✅南昌资源 ✅惠州资源 ✅义乌资源 ✅武汉资源 ✅东北资源 ✅海南资源 ✅天津资源 👨‍👩‍👧‍👦山东群组 🛜其它地区

29 Oct 2026, 13:59 UTC165 viewsread 30 October 2026

✅西安资源 ✅昆明资源 ✅南昌资源 ✅惠州资源 ✅义乌资源 ✅武汉资源 ✅东北资源 ✅海南资源 ✅天津资源 👨‍👩‍👧‍👦山东群组 🛜其它地区

28 Oct 2026, 18:59 UTC687 viewsread 29 October 2026

✅西安资源 ✅昆明资源 ✅南昌资源 ✅惠州资源 ✅义乌资源 ✅武汉资源 ✅东北资源 ✅海南资源 ✅天津资源 👨‍👩‍👧‍👦山东群组 🛜其它地区

Showing the 12 most recent of 102 posts we hold for @sosuokV. 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 edited after publishing

@sosuokV edited 1 post after it first published — the same permalink now carries different wording than the one this register originally read, caught because our own crawl held a copy of the earlier text.

An edit is not deception. Typo fixes, price updates and corrections look exactly like this too — this register can tell you the wording changed and when, not why. How this is measured.

First edit seen
16 October 2026
Most recent edit
16 October 2026

Posts recorded as deleted after publishing

We recorded 7 posts on @sosuokV 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
22 August 2026
Most recent seen missing
14 October 2026
Median time before seen missing
44 hours
Seen missing in the last 30 days
3

Mentions

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

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

“济南青岛公开资源(认证)” (@sosuokV), 43,827 subscribers as measured 7 November 2026. Telegram Register, tgregister.com/channel/sosuokV.

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.