Telegram RegisterThe public register of Telegram
Telegram profile photo for 泉城济南电报问答吧 🅨

Channel

泉城济南电报问答吧 🅨

@jinanwen

2 usernames

On this record: Growth · Engagement · Reactions · Posts · Citations · Cite this entry

11,733subscribers

+234 since we began measuring on 11 August 2026

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

Register entry

Telegram ID-1002273329583
TypeChannel
Usernames@jinanwen @wendaba
CreatedBetween 1 September 2024 and 31 March 2025— estimated from Telegram’s id allocation, not measured. How this range is calculated.
First recorded11 August 2026
Last confirmed live18 August 2026
Measurements held14
Confirmed unchanged1 time, most recently 18 August 2026
On Telegramt.me/jinanwen

Growth

11,49911,73311,61611 August 2026 — 11,499 subscribers11 August 2026 — 11,511 subscribers11 August 2026 — 11,522 subscribers12 August 2026 — 11,527 subscribers12 August 2026 — 11,537 subscribers13 August 2026 — 11,551 subscribers14 August 2026 — 11,589 subscribers14 August 2026 — 11,604 subscribers15 August 2026 — 11,634 subscribers15 August 2026 — 11,646 subscribers16 August 2026 — 11,679 subscribers17 August 2026 — 11,694 subscribers17 August 2026 — 11,716 subscribers18 August 2026 — 11,733 subscribers11 August 202618 August 2026
14 measurements spanning 7 days, net +234. 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 11,464–11,768 and does not start at zero.
Measurement log — every subscribers count we have recorded
Measured (UTC)SubscribersChange
18 Aug 2026, 13:2311,733+17
17 Aug 2026, 19:2511,716+22
17 Aug 2026, 11:3311,694+15
16 Aug 2026, 20:1511,679+33
15 Aug 2026, 20:5611,646+12
15 Aug 2026, 08:5411,634+30
14 Aug 2026, 12:4811,604+15
14 Aug 2026, 01:1611,589+38
13 Aug 2026, 03:4811,551+14
12 Aug 2026, 17:4711,537+10
12 Aug 2026, 03:3211,527+5
11 Aug 2026, 19:5811,522+11
11 Aug 2026, 15:1611,511+12
11 Aug 2026, 13:1711,499first reading

Engagement

28 posts held, back to 29 July 2026the reader has not yet reached the start of this channel’s public history, so older posts may sit further back, unread. Read across 9 pagesof Telegram’s post history, 20 posts per page.

ERR · 30 days
46.6%
avg views ÷ 11,733 subscribers
Avg views / post
5,470
28 posts measured
Reaction rate
0.019%
reactions ÷ views · ER floor
Posts in window
28
of 28 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 22 of 28 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 18 August 2026
Posts held28 (29 July 202618 August 2026)
Views total153,047
Reactions total23
Forwards / commentsnot exposed by the public surface — not measured, not estimated
Readings taken18 Aug 2026, 08:43 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.

Reaction mix

23 reactions across 12 posts, in 1 kind.

Every reaction kind recorded on the sample, most used first
ReactionCountShareShare, drawn
23100.0%

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

Measured over the 28 most recent posts we hold, published 29 July 2026 to 18 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.

Recent posts

18 Aug 2026, 07:43 UTC210 viewsread 18 August 2026

#济南 #提问 点击提问→ @zitoubot 请问各位大佬们,假设你们飞机上约一次个人出击,在这个过程中一共大概支出(像什么性安全押金,tt钱以及课费等)多少元子啊。 via 匿名 📎 查看原文

17 Aug 2026, 22:29 UTC897 views0 reactionsread 18 August 2026

#济南 #提问 点击提问→ @zitoubot 私影有人去过吗?有什么服务?怎么样 via 1111 7777 📎 查看原文

17 Aug 2026, 14:47 UTC≈1,370 views1 reactionsread 18 August 2026

#济南 #提问 点击提问→ @zitoubot 想问下各位大佬,在家用梯子上不去,用公司网络就可以上梯子,这是怎么回事?有没有大佬懂得,求指导 via b oyce 📎 查看原文

1

17 Aug 2026, 07:48 UTC≈1,740 viewsread 18 August 2026

#济南 #提问 点击提问→ @zitoubot 92默认都能摸🐻吗? via coconut 📎 查看原文

17 Aug 2026, 04:36 UTC≈1,930 views1 reactionsread 18 August 2026

#济南 #提问 点击提问→ @zitoubot 济南最近怎么了,严打吗?很多群都不见了。还有哪些可以去的地方推荐吗? via LiuXiang Chu 📎 查看原文

1

16 Aug 2026, 14:08 UTC≈2,430 views0 reactionsread 18 August 2026

#济南 #提问 点击提问→ @zitoubot 想问问各位老哥,约炮可能会被认定成嫖娼吗?就比如去酒吧一夜情碰上了女的是🐔,但是没有金钱交易,被查房了会被当成pc吗?需要注意些什么,求大佬解答 via 五阴炽盛 📎 查看原文

16 Aug 2026, 11:53 UTC≈2,550 views0 reactionsread 18 August 2026

#济南 #提问 点击提问→ @zitoubot 各位济南xdm,从来没玩过,想找个上门,问一下找上门的流程和注意事项是什么啊?会被查到吗? via 匿名 📎 查看原文

11 Aug 2026, 15:01 UTC≈5,610 viewsread 18 August 2026

#济南 #提问 点击提问→ @zitoubot 有没有有见识的大哥知道三亚游艇有啥玩法吗,气氛组可以干什么呀 via 匿名 📎 查看原文

10 Aug 2026, 11:10 UTC≈6,130 views2 reactionsread 18 August 2026

#济南 #提问 点击提问→ @zitoubot 济南夜的都是三次吗?有没有不限次数的 via ming Jon 📎 查看原文

2

10 Aug 2026, 07:22 UTC≈6,030 views0 reactionsread 18 August 2026

#济南 #提问 点击提问→ @zitoubot 老师儿们 工作原因需要在泰安呆一段时间,手里一下子没资源了,来回跑不值当的,刚加了个泰安修车群,不知道靠不靠谱,有没有屌大的说说或者给指指路,先撸为敬! via 贝塔 📎 查看原文

10 Aug 2026, 01:40 UTC≈5,640 views0 reactionsread 18 August 2026

#济南 #提问 点击提问→ @zitoubot 大佬们,明明在飞机上约好了,找了个个人兼职,为什么还要电话呢,飞机上都能联系呀😂 via liuxiao 📎 查看原文

7 Aug 2026, 15:14 UTC≈7,230 views2 reactionsread 18 August 2026

#济南 #提问 点击提问→ @zitoubot 今晚哪里有站街的,有出击的大diao吗? via ️ Jaime 📎 查看原文

2

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

Citation-graph rank

Citation-graph rank — 628,949 of 1,549,704entries in the measured graph. A weighted position computed from the forward and mention edges below — republished posts weigh more than named mentions — and recomputed periodically, over the whole graph. Published only as this ordinal position, never as a score: a position is a fact, and a score printed beside one channel’s name would read as a verdict this register does not make. The two counts beneath stay separate for the same reason mentions are never summed with forwards anywhere else on this page — a named-by count costs nothing to manufacture. The top 100 by this measure, or how it is computed.

Mentions

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.

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

“泉城济南电报问答吧 🅨” (@jinanwen), 11,733 subscribers as measured 18 August 2026. Telegram Register, tgregister.com/channel/jinanwen.

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.