Telegram RegisterThe public register of Telegram
Telegram profile photo for ••• forms 🥢

Channel

••• forms 🥢

@reiportform

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

84subscribers

+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-1001918380183
TypeChannel
Username@reiportform
Created22 June 2023measured — dated from the channel’s first post
First recorded9 August 2026
Last confirmed live17 September 2026
Measurements held4
Confirmed unchanged4 times, most recently 17 September 2026
On Telegramt.me/reiportform

Growth

838483.59 August 2026 — 84 subscribers9 August 2026 — 84 subscribers16 August 2026 — 83 subscribers24 August 2026 — 84 subscribers9 August 202624 August 2026
4 measurements spanning 14 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 83–84 and does not start at zero.
Measurement log — every subscribers count we have recorded
Measured (UTC)SubscribersChange
24 Aug 2026, 00:3684+1
16 Aug 2026, 22:0383-1
9 Aug 2026, 18:3084no change
9 Aug 2026, 18:1784first reading

Engagement

17 posts held, back to 22 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 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 17 posts for this entry, the most recent from 21 March 2026. An engagement rate over an empty window would be a number about nothing.

Recent posts

21 Mar 2026, 14:03 UTC471 viewsread 9 August 2026

note : monitoring form is different from report form. use the correct form and fill it out correctly and com- pletely. double checking the form before sending is a must. read also the pinned post from this channel before magfill-up ng form.

7 Dec 2023, 06:05 UTC≈4,570 viewsread 9 August 2026

— monitoring form ! • tg username: • account email: • password: • solo/shared: • profile: • device brand & model : • location:

28 Jun 2023, 01:24 UTC≈3,840 viewsread 9 August 2026

⌗ netflix inco pass form : email: recent password: date availed: solo prof or shared prof: profile name & pin: screenshot of proof of issue & vouch: • send form in one bubble chat only. • incomplete details will be ignored. .

28 Jun 2023, 01:22 UTC≈3,290 viewsread 9 August 2026

⌗ other prem computation : email : gc deets : what prem : amount paid ÷ 30 days × .7 (service fee) × remaining days —————————— = refund amount kindly show me the breakdown as to how you derived with the amount you calculated. .

28 Jun 2023, 01:21 UTC≈3,100 viewsread 9 August 2026

⌗ netflix rf computation : email : gc deets : amount paid ÷ 30 days × .7 (service fee) × remaining days —————————— = refund amount kindly show me the breakdown as to how you derived with the amount you calculated. .

28 Jun 2023, 01:21 UTC≈3,040 viewsread 9 August 2026

⌗ other prems report form username : what account : first email : email : password : subscription : solo / shared : purchased price : date purchased : date reported : remaining days : issue : proof of issue (screenshot) : proof of vouch (screenshot) : send in one bubble chat only .

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

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

“••• forms 🥢” (@reiportform), 84 subscribers as measured 24 August 2026. Telegram Register, tgregister.com/channel/reiportform.

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.