Hi! Keysha here, see to @fouadmschi for concerns and updates! Ty!

Channel
Fouires' Reports
@foureps
On this record: Topic · Growth · Engagement · Posts · Citations · Cite this entry
32subscribers
-2 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 | -1003799737802 |
|---|---|
| Type | Channel |
| Username | @foureps |
| Created | Between 1 February 2026 and 6 March 2026 — estimated from Telegram’s id allocation, not measured. How this range is calculated. |
| First recorded | 11 August 2026 |
| Last confirmed live | 3 October 2026 |
| Measurements held | 4 |
| Confirmed unchanged | 1 time, most recently 3 October 2026 |
| On Telegram | t.me/foureps |
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 3 October 2026 and assigned it the closest of 31 fixed categories, at 98% 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
| Measured (UTC) | Subscribers | Change |
|---|---|---|
| 3 Oct 2026, 08:59 | 32 | -1 |
| 17 Aug 2026, 11:16 | 33 | -1 |
| 11 Aug 2026, 00:15 | 34 | no change |
| 9 Aug 2026, 21:45 | 34 | first reading |
Engagement
20 posts held, back to 6 March 2026 — the reader has not yet reached the start of this channel’s public history, so older posts may sit further back, unread. Read across 1 page of 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 May 2026. An engagement rate over an empty window would be a number about nothing.
Recent posts
refunds section
Signed ౨ৎ. ࣪ chipi ~ jwu! up mga chats di napansin 💌
attention for capcut buyers: new update from supplier: will wait refunds and then direct ko sa inyo. may 2 days pa left sa subs niyo so pwede pa humabol yung refunds ni supp heads up lang to! ❤️
Signed ౨ৎ. ࣪ chipi ~ closed po 05/08/26, check chan
reports all cleared except refunds, if may report ka na hindi na fix paki up, strictly NO DM FIXING. Di ko na kini-cater yan since natatabunan na lahat imortant chats ko
Signed ᰋ. ࣪ chipi ~ offline / zzz
pano ko ba yan iayos if di nyo ilalagay password? okay lang naman coding if login and upon purchase pero if for reports na aanhin ko ba code if hindi ko ma login ites 😅
Signed ᰋ. ࣪ chipi ~ CHECK CHANNEL and NO SPAM
Hi, for the last time, incorrect form sa reports = void. Paulit ulit nalang ba ako mag remind?
Signed ᰋ. ࣪ chipi ~ CHECK CHANNEL and NO SPAM
FOR THE LAST TIME, INCORRECT FORM OR EVEN KULANG NA FORM, WILL AUTOMATICALLY BE VOIDED!
can code ulit both accs, send direct report to the bottom chat below the channel WITH MONITORING FORM AND VOUCH NA VALID.
REMINDERS: NO 3RD WARNING, DIRECT VOID IF LALAGPAS 2ND WARNING ‼️
Fouires' Reports pinned «⚠️‼️ PLEASE READ EVERYTHING. spotify rules, click me! shop reminders, click me! shop terms, click me! void terms, click me! for reports: @foureps for concerns: @pichimps»
up po, di po tayo parehas time mag online, ma delay po talaga pagfix sa prems nyo if ayaw nyo magbigay password, ma change pass nyo naman sha pagkatapos. okay lang naman di kayo mag provide password, expect lang matagalan talaga pag fix nyan kasi iintayin nyo pa ako ma online and kung ano schedule sa fixing ko di ba?
Fouires' Reports pinned «can direct here na sa baba ng channel direct messages»
Showing the 12 most recent of 20 posts we hold for @foureps. 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.
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.
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 3 October 2026 — this entry's latest reading, not the date you are reading this.
“Fouires' Reports” (@foureps), 32 subscribers as measured 3 October 2026. Telegram Register, tgregister.com/channel/foureps.
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.