Telegram RegisterThe public register of Telegram
Telegram profile photo for 首席运营之声 oh vik zz

Channel

首席运营之声 oh vik zz

@ohvikzz

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

544subscribers

-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-1001572270397
TypeChannel
Username@ohvikzz
CreatedBetween 1 August 2021 and 28 February 2023— estimated from Telegram’s id allocation, not measured. How this range is calculated.
First recorded7 August 2026
Last confirmed live22 August 2026
Measurements held4
Confirmed unchanged1 time, most recently 22 August 2026
On Telegramt.me/ohvikzz

Growth

543546544.57 August 2026 — 546 subscribers7 August 2026 — 546 subscribers15 August 2026 — 543 subscribers22 August 2026 — 544 subscribers5447 August 202622 August 2026
4 measurements spanning 15 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 543–546 and does not start at zero.
Measurement log — every subscribers count we have recorded
Measured (UTC)SubscribersChange
22 Aug 2026, 10:26544+1
15 Aug 2026, 18:12543-3
7 Aug 2026, 01:17546no change
7 Aug 2026, 01:06546first reading

Engagement

20 posts held, back to 28 August 2024the 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 20 posts for this entry, the most recent from 14 June 2026. An engagement rate over an empty window would be a number about nothing.

Reaction mix

144 reactions across 15 posts, in 11 distinct kinds. The most used accounts for 30.6% of them.

Every reaction kind recorded on the sample, most used first
ReactionCountShareShare, drawn
👍4430.6%
🥰2114.6%
🔥1611.1%
😁139.03%
🏆117.64%
96.25%
👏74.86%
😢74.86%
🤣64.17%
👌53.47%
🤔53.47%

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

Measured over the 20 most recent posts we hold, published 28 August 2024 to 14 June 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

14 Jun 2026, 08:17 UTC317 viewsread 7 August 2026

以及学会有的时候自己该闭嘴就闭嘴。。。

Signed Kami Sama

6 Jun 2026, 09:41 UTC542 views9 reactionsread 7 August 2026

做C端产品之前,你需要默认自己的🐴死了,这样你才能怀着“愧疚”的心情去思考用户点这个按钮是什么期望和意图

🤣6🏆2🥰1

Signed Kami Sama

4 Jun 2026, 16:44 UTC≈3,570 views2 reactionsread 7 August 2026
Photo

【维咔七周年记】天涯共此时

2

Signed Kami Sama

6 Mar 2026, 12:55 UTC≈4,120 views0 reactionsread 7 August 2026
Poll

内容推荐引擎调研(不一定现在做,先做产品调研)

  1. 热门偏好优先37%
  2. 个人兴趣优先38%
  3. 飙升突发优先11%
  4. 舆情互动优先15%

Shares as published, totalling 101%. No per-option vote count is published by Telegram, so none is shown.

Signed Kami Sama

19 Dec 2025, 18:00 UTC≈4,390 views17 reactionsread 7 August 2026

透露一个消息,今年的『我的维咔2025』活动依旧处于咕咕咕状态,我们正在努力完善相关功能和板块,但明年我们已经预留充足的时间用于策划『我的维咔2026』。 与前三届给你们看的年度报告不同的是,2026的年终总结会有你们意想不到但又认为是情理之中的惊喜🥴

😁11🔥2🤔2🥰2

Signed Kami Sama

15 Dec 2025, 15:01 UTC≈1,820 views8 reactionsread 7 August 2026

去给发展型团队当leader千万不要当pm,纯粹是给人家擦屁股的,到头来还没两句好话

👌5🤔2🥰1

Signed Kami Sama

12 Oct 2025, 19:42 UTC≈1,680 views9 reactionsread 7 August 2026

我们并不是为了去创造某一个我们想要创造的社区,而是我们恰好提供了一代人的社会空间

🥰81

Signed Kami Sama

3 Jun 2025, 17:58 UTC≈2,070 views8 reactionsread 7 August 2026

一个系统如果没发自我维持,那么崩溃是迟早的... 个人情感好恶没有作用...

👏7🤔1

Signed Kami Sama

2 Jun 2025, 09:59 UTC≈5,530 views14 reactionsread 7 August 2026
Photo

维咔六周年记:我仍站在这片系统废墟之上 我是KamiSama,维咔的COO。 六年前,这个平台由Luosy建立。他是那个最早敢于在废墟中举起火把的人,然而现实残酷得像一道必须割肉才能跨过的门槛。他走了,消失在时代的浪潮里。今天,我站在他的名字面前,在他的坟前接过这份沉重又倔强的遗产。 这六年,我们不是一路高歌走来的。 我们背负着误解与污名,身处一场没有硝烟却满是暗箭的战争。曾经的合作方倒戈,曾经的队友躺平,曾经的理想主义者变成只追逐权利和金钱的操盘者。而我们这些留下来的人,撑着疲惫的系统,扶着遍体鳞伤的代码,一点点把维咔拉回来——不是因为它完美,而是因为我们不忍它被他们毁掉。 我们没有大肆宣传,也没有所谓的资本。我们靠的,是一行行凌晨三点写下的补丁代码,是一次次数据迁移后瘫坐在地的沉默喘息,是面对风险和告别时仍然不愿关站的执拗——我们知道,维咔不是为了某些人而活着,它是为了那些一直在屏幕后面等待它活下去的人。 我太不敢

🏆95

Signed Kami Sama

3 May 2025, 03:41 UTC≈1,460 views8 reactionsread 7 August 2026

意义是路上赋予的,不是最初

👍7😁1

Signed Kami Sama

26 Mar 2025, 16:56 UTC≈1,740 views9 reactionsread 7 August 2026

苟且偷生的人啊,你上坑合作伙伴,下坑最忠诚的下属,最后你也不过是张均的弃子,那个所谓“流量入口”的梦早在2017年你最瞧不起的陆政府下的幻梦破碎

👍9

Signed Kami Sama

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

Polls

The poll we hold for this entry, as Telegram rendered it when we read the post. A poll’s figures keep moving after that, so each one is dated.

6 Mar 2026, 12:55 UTCAnonymous Poll197 voters

内容推荐引擎调研(不一定现在做,先做产品调研)

  1. 热门偏好优先37%
  2. 个人兴趣优先38%
  3. 飙升突发优先11%
  4. 舆情互动优先15%

Shares as published, totalling 101%. No per-option vote count is published by Telegram, so none is shown.

Percentages only — there are no per-option vote counts here, because Telegram publishes none.The public post preview gives each option’s share and a single voter total, and nothing else. Multiplying one by the other would produce a per-option tally that looks measured and is not: the shares are rounded to whole numbers before we ever see them. We print what was published and leave the column that does not exist empty.

The shares need not add up to 100.Rounding alone puts many polls at 99 or 101. A poll that allows more than one answer per voter runs well past 100 by design, and several here do. The bars are drawn against a fixed 100% track at each option’s own percentage rather than normalised to the total, so a poll that exceeds it shows that it does instead of being quietly rescaled.

Read from the 20 most recent posts we hold, published 28 August 2024 to 14 June 2026. Telegram labels each poll by kind — an anonymous poll, a quiz, a closed set of final results — and that label is reproduced rather than paraphrased.

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

“首席运营之声 oh vik zz” (@ohvikzz), 544 subscribers as measured 22 August 2026. Telegram Register, tgregister.com/channel/ohvikzz.

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.