Telegram RegisterThe public register of Telegram
Telegram profile photo for pfizy

Channel

pfizy

@pfizy

Has discussion group

On this record: Topic · Growth · Engagement · Citations · Cite this entry

2,620subscribers

+1,406 since we began measuring on 9 August 2026

Risers and fallers across the register · movement among entries of 1,000–3,162.

Register entry

Telegram ID-1003863766705
TypeChannel
Username@pfizy
Descriptionлс - @chifkif300
CreatedBetween 1 February 2026 and 31 July 2026 — estimated from Telegram’s id allocation, not measured. How this range is calculated.
First recorded14 September 2026
Last confirmed live14 September 2026
Measurements held13
On Telegramt.me/pfizy

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 15 September 2026 and assigned it the closest of 31 fixed categories, at 100% 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 why it has no browse page of its own yet.

Growth

1,2142,6201,9179 August 2026 — 1,214 subscribers10 August 2026 — 1,269 subscribers13 August 2026 — 1,486 subscribers17 August 2026 — 1,691 subscribers20 August 2026 — 1,878 subscribers23 August 2026 — 2,078 subscribers26 August 2026 — 2,134 subscribers30 August 2026 — 2,191 subscribers2 September 2026 — 2,376 subscribers6 September 2026 — 2,482 subscribers10 September 2026 — 2,537 subscribers14 September 2026 — 2,620 subscribers14 September 2026 — 2,620 subscribers9 August 202614 September 2026
13 measurements spanning 36 days, net +1,406. 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 1,003–2,831 and does not start at zero.
Measurement log — every subscribers count we have recorded
Measured (UTC)SubscribersChange
14 Sept 2026, 15:002,620no change
14 Sept 2026, 14:582,620+83
10 Sept 2026, 20:422,537+55
6 Sept 2026, 04:162,482+106
2 Sept 2026, 02:172,376+185
30 Aug 2026, 02:582,191+57
26 Aug 2026, 22:072,134+56
23 Aug 2026, 13:062,078+200
20 Aug 2026, 09:231,878+187
17 Aug 2026, 12:421,691+205
13 Aug 2026, 22:381,486+217
10 Aug 2026, 08:111,269+55
9 Aug 2026, 18:461,214first reading

Engagement

Posts not read yet. This entry is on the register from its profile alone; the post reader has not reached it. Engagement figures appear here once posts have actually been measured — we do not publish a rate before we have the readings behind it.

Forward network

Republished by

Channels on the register that have forwarded this channel's posts into their own feed.

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.

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

“pfizy” (@pfizy), 2,620 subscribers as measured 14 September 2026. Telegram Register, tgregister.com/channel/pfizy.

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.