Telegram RegisterThe public register of Telegram
Telegram profile photo for STORE RESS FB

Channel

STORE RESS FB

@stokressfb

On this record: Growth · Engagement · What this channel posts · Posts · Citations · Handles named that no longer answer · Cite this entry

14subscribers

+0 since we began measuring on 10 August 2026

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

Register entry

Telegram ID-1001523267924
TypeChannel
Username@stokressfb
CreatedBetween 1 August 2021 and 18 January 2023 — estimated from Telegram’s id allocation, not measured. How this range is calculated.
First recorded12 August 2026
Last confirmed live1 September 2026
Measurements held2
On Telegramt.me/stokressfb

Growth

1410 Aug 2026, 22:45 — 14 subscribers12 Aug 2026, 02:01 — 14 subscribers10 Aug 2026, 22:4512 Aug 2026, 02:01
2 measurements spanning 1 day. 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 13–15 and does not start at zero.
Measurement log — every subscribers count we have recorded
Measured (UTC)SubscribersChange
12 Aug 2026, 02:0114no change
10 Aug 2026, 22:4514first reading

Engagement

15 posts held, back to 18 January 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 15 posts for this entry, the most recent from 15 February 2023. An engagement rate over an empty window would be a number about nothing.

What this channel posts

Photos
24

Lifetime counters from Telegram’s own channel header, read 12 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

5 Feb 2023, 18:08 UTC197 viewsread 12 August 2026
Photo

Monkos log FB 7k Amanin sendiri @naspad_pagisore #SOLD

4 Feb 2023, 11:59 UTC378 viewsread 12 August 2026
Photo

SPEK PM LOG MONSEP GMAIL POLOS ALKOS FREE SERVER AJAIB HARGA? 50k PM @naspad_pagisore #SOLD

19 Jan 2023, 19:23 UTC331 viewsread 12 August 2026
Photo

Entar bangun tidur open JASTEB web dari gua tinggal send Gmail 7k 30+ | 15k 99+ | 25k 199+. @naspad_pagisore

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

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

“STORE RESS FB” (@stokressfb), 14 subscribers as measured 12 August 2026. Telegram Register, tgregister.com/channel/stokressfb.

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.