Telegram RegisterThe public register of Telegram
Telegram profile photo for BIO - Fail_ETK

Channel

BIO - Fail_ETK

@bio_fail0etk

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

25subscribers

+7 since we began measuring on 8 August 2026

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

Register entry

Telegram ID-1002402309221
TypeChannel
Username@bio_fail0etk
Created13 February 2025measured — dated from the channel’s first post
First recorded11 August 2026
Last confirmed live4 September 2026
Measurements held5
Confirmed unchanged1 time, most recently 4 September 2026
On Telegramt.me/bio_fail0etk

Growth

182521.58 August 2026 — 18 subscribers11 August 2026 — 18 subscribers16 August 2026 — 19 subscribers22 August 2026 — 23 subscribers4 September 2026 — 25 subscribers8 August 20264 September 2026
5 measurements spanning 27 days, net +7. 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 17–26 and does not start at zero.
Measurement log — every subscribers count we have recorded
Measured (UTC)SubscribersChange
4 Sept 2026, 11:2025+2
22 Aug 2026, 11:3823+4
16 Aug 2026, 02:2619+1
11 Aug 2026, 18:4618no change
8 Aug 2026, 10:4618first reading

Engagement

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

Recent posts

13 Feb 2025, 10:00 UTC854 viewsread 11 August 2026

Чё такое био.. 🔍 База? Актуальные никнеймы: Fail | E_TK ; Fail0E_TK ; Фаил0Е_ТК ; FailETK ; Fail_ETK ; Fail0Yosef Устаревшие, но, возможные никнеймы: LaimoviyFreddy | EsickTheCat | LFTB | E_TC Полных лет - 16 Дата когда я ёбнулся с луны - 04.05.2010 Юзаю Blender последних версий, доступных в стим Конфиг моего пк: i7-13700KF RTX 5080 32гб DDR5 RAM 1тб m2 диск C 2тб m2 диск D Миша. Russian bro Speak English on b

Showing the 2 most recent of 2 posts we hold for @bio_fail0etk. 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

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

“BIO - Fail_ETK” (@bio_fail0etk), 25 subscribers as measured 4 September 2026. Telegram Register, tgregister.com/channel/bio_fail0etk.

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.