Telegram RegisterThe public register of Telegram

Channel

BiBimPow Archive

@PimPowWie

On this record: Growth · Engagement · What this channel posts · Posts · Citations · Cite this entry

4subscribers

+0 since we began measuring on 9 August 2026

Risers and fallers across the register · movement among entries of Under 1,000.

Register entry

Telegram ID-1001419202938
TypeChannel
Username@PimPowWie
DescriptionRandom but esp for proof, testi and list order. Connected to @BiBimPow
CreatedBetween 1 April 2019 and 30 September 2021— estimated from Telegram’s id allocation, not measured. How this range is calculated.
First recorded13 August 2026
Last confirmed live13 August 2026
Measurements held2
On Telegramt.me/PimPowWie

Growth

49 August 2026 — 4 subscribers13 August 2026 — 4 subscribers9 August 202613 August 2026
2 measurements spanning 3 days. 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 3–5 and does not start at zero.
Measurement log — every subscribers count we have recorded
Measured (UTC)SubscribersChange
13 Aug 2026, 04:314no change
9 Aug 2026, 20:484first reading

Engagement

16 posts held, back to 29 June 2023the 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 16 posts for this entry, the most recent from 2 July 2023. An engagement rate over an empty window would be a number about nothing.

What this channel posts

Photos
66
Links
1

Lifetime counters from Telegram’s own channel header, read 13 August 2026 — not the date at the top of this page, which is when the subscriber count was last read. Below Telegram’s rounding threshold, so these counts are exact.

Recent posts

2 Jul 2023, 14:28 UTCviews —

BiBimPow Archive pinned «‼️MUTUALS CLEANING TIME‼️ 💐Use the format below🐇 username account : @ username channel : @ contact hfw : @ link mutual's data : t.me/»

2 Jul 2023, 14:28 UTC64 viewsread 13 August 2026

‼️MUTUALS CLEANING TIME‼️ 💐Use the format below🐇 username account : @ username channel : @ contact hfw : @ link mutual's data : t.me/

2 Jul 2023, 12:12 UTC42 viewsread 13 August 2026
Forwarded from @BiBimPowPhoto

#Result #Poweans x #Scrembow Pokoknya kepuasan Bimmie number 1 atau bahkan kalau ada yang lebih baik dari 1 Wawa pilih angka itu HAHAHAHA

30 Jun 2023, 17:40 UTC53 viewsread 13 August 2026
Photo

Hihihihihi #Result #Poweans #Screambow , beli poweans bonus scribble kpn lgi😍

Showing the 12 most recent of 16 posts we hold for @PimPowWie. 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 — 169,376 of 1,350,102entries 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.

Forward network

Republishes

Channels on the register whose posts this channel has forwarded.

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

“BiBimPow Archive” (@PimPowWie), 4 subscribers as measured 13 August 2026. Telegram Register, tgregister.com/channel/PimPowWie.

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.