Channel

🪖 // ивент, и где я емае || 𝘶𝘯𝘥𝘦𝘢𝘥 𝘴𝘰𝘭𝘥𝘪𝘦𝘳.. ? #янепяткасолдат🖕🖕🖕🖕🖕

@FootSold1er_sea

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

26subscribers

+6 since we began measuring on 12 August 2026

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

Register entry

Growth

Engagement

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

Recent posts

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

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

“🪖 // ивент, и где я емае || 𝘶𝘯𝘥𝘦𝘢𝘥 𝘴𝘰𝘭𝘥𝘪𝘦𝘳.. ? #янепяткасолдат🖕🖕🖕🖕🖕” (@FootSold1er_sea), 26 subscribers as measured 19 September 2026. Telegram Register, tgregister.com/channel/FootSold1er_sea.

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.