Telegram RegisterThe public register of Telegram
Telegram profile photo for keopi reports

Channel

keopi reports

@keopireports

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

605subscribers

-1 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-1001597245164
TypeChannel
Username@keopireports
CreatedBetween 1 August 2021 and 28 February 2023— estimated from Telegram’s id allocation, not measured. How this range is calculated.
First recorded8 August 2026
Last confirmed live15 August 2026
Measurements held3
Confirmed unchanged2 times, most recently 15 August 2026
On Telegramt.me/keopireports

Growth

605606605.57 Aug 2026, 20:49 — 606 subscribers8 Aug 2026, 03:04 — 606 subscribers8 Aug 2026, 03:26 — 605 subscribers7 Aug 2026, 20:498 Aug 2026, 03:26
3 measurements taken within a single day, net -1. 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 605–606 and does not start at zero.
Measurement log — every subscribers count we have recorded
Measured (UTC)SubscribersChange
8 Aug 2026, 03:26605-1
8 Aug 2026, 03:04606no change
7 Aug 2026, 20:49606first reading

Engagement

19 posts held, back to 21 April 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.

ERR · 30 days
14.0%
avg views ÷ 605 subscribers
Avg views / post
85.0
1 post measured
Reaction rate
this channel exposes no reaction counts
Posts in window
1
of 19 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.

What these figures were computed from
WindowRolling 30 days · latest post in window 21 July 2026
Posts held19 (21 April 202421 July 2026)
Views total85
Reactions total
Forwards / commentsnot exposed by the public surface — not measured, not estimated
Readings taken8 Aug 2026, 03:04 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.

Recent posts

10 Mar 2026, 07:11 UTC569 viewsread 8 August 2026

HI! MAY NEW GCASH NUMBER PO AKO, PLEASE ASK MUNA BEFORE SENDING YOUR PAYMENTS. TYSM! @L0VEIMS0L

14 Jun 2025, 09:28 UTC≈1,530 viewsread 8 August 2026

this will be the last time na mag'reremind ako regarding sa changing of password & sa pag'checheck ng rules sa rules channel. BASAHIN PO NINYO BUONG ORDER FORM, HINDI LANG PO SANA FOCUS SA EMAIL AT PASSWORD. starting today, lahat ng reports sa mga premium apps na need i'change ang password, automatic void warranty na. hindi na ako mag'wawarning pa. kasi ako din ang na'hahassle sa pag'rereport sa supplier. be mindful

10 Jun 2025, 06:10 UTC≈1,090 viewsread 8 August 2026

please naman, paki'basa naman ng rules! nakalagay naman na po sa order form na, "follow rules ; @astrarules" kung hindi po napipindot 'yung link ng rules, pwede niyo naman hanapin eh or sabihin na hindi napi pindot. lalo na spotify, strictly po iyan na need i'change pass unless sinabi na hindi or bawal i'change pass. 2 times nang may nag'report na hindi nag'change pass ha? next time, auto void na kahit bagong avail n

7 Apr 2025, 22:36 UTC≈1,610 viewsread 8 August 2026
Photo

NEW CHANNEL @lovepeonie (1st pic) OLD CHANNEL got banned (2nd pic) sayang subs bwiset sksksksk 😭

8 Feb 2025, 00:18 UTC≈1,510 viewsread 8 August 2026

ALSO, REMIND KO LANG DIN NA HINDI STRAIGHT SUB LAHAT NG PREMIUMS DITO AT INDICATED PO 'YAN SA RATES. MONTHLY REPLACEMENTS PO LAHAT AND NEED NIYO PO 'YAN I'REPORT SA TAMANG REPORT ACC AND MAKE SURE NA COMPLETE LAGI ANG FORMS NIYO DAHIL I'IGNORE KO 'YAN IF INCOMPLETE. MAGIGING STRICT NA KO SA REPORTS AT SA RULES NA DAHIL ANG HINDING NAGBABASA. AGAIN, PLEASE DO MAKE READING A HABIT PO.

7 Feb 2025, 23:14 UTC≈1,340 viewsread 8 August 2026

REMINDER TO ALL BUYERS ESPECIALLY SA MGA PREMIUMS NA NEED I'CHANGE ANG PASSWORD, STARTING TODAY PO ONCE MA'CHECK KO 'YANG REPORTS AT HINDI NAG'CHANGE PASS, AUTO VOID NA. HINDI KO NA KAYO WAWARNINGAN AT PAGBIBIGYAN PA DAHIL 'YUN NAMAN PO TALAGA ANG RULES. SO KUNG HINDI NIYO PINAPANSIN 'YUNG NASA IBAIBANG PART NA NAKALAGAY SA ORDER FORM, IT'S UR FAULT, NOT MINE. NAKAKAPAGOD DIN PO MAG'PAALALA SAINYO TAS KAPAG VOIDED KA

29 Oct 2024, 05:00 UTC≈2,020 viewsread 8 August 2026

I will not entertain anymore sa mga mag'tatanong ng updates sa dms lalo na if posted naman dito 'yung updates. matuto pong mag'check ng report channel. thank you. ⋆ cess

30 Aug 2024, 06:22 UTC≈2,400 viewsread 8 August 2026

🌸 SCHEDULE FOR NETFLIX CODING (SIGN-IN CODE OR NETFLIX HOUSEHOLD) 🌸 schedule for mon, wed, fri 9:00am-2:00pm schedule for tues, thurs 9:00am-10:00am schedule for sat, sun 9:00am-10:00am 4:00pm-5:00pm 9:30pm onwards — this schedule is from the supplier, also eto din available time namin ni jl since may work kami sa gabi. this may also vary if busy supplier or kami ni jl. 🌸 SCHEDULE FOR DISNEY CODING 🌸 — for disn

23 Jun 2024, 02:08 UTC≈2,410 viewsread 8 August 2026

please kindly click this before reporting. we will not entertain those reports na 'di susunod sa mga nakalagay dito. also, do check the proper way of reporting. thanks!

22 Jun 2024, 12:32 UTC≈2,480 viewsread 8 August 2026
Photo

🎀 proper way of reporting ! 🎀 incomplete details of report/ not following this format = ignored

Showing the 12 most recent of 19 posts we hold for @keopireports. 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 — 328,895 of 1,481,306entries 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.

Names

Channels on the register whose handles appear in this channel's posts.

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

“keopi reports” (@keopireports), 605 subscribers as measured 8 August 2026. Telegram Register, tgregister.com/channel/keopireports.

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.