27 Feb 2026, 09:40 UTCviews —
Posted without readable text
Channel
BugOrFeature 💭
@bgorft
On this record: Growth · Engagement · What this channel posts · Posts · Citations · Cite this entry
2subscribers
+0 since we began measuring on 7 August 2026
Risers and fallers across the register · movement among entries of Under 1,000.
Register entry
| Telegram ID | -1001266260430 |
|---|---|
| Type | Channel |
| Username | @bgorft |
| Description | Sometimes you feel that encounter a bug but... |
| Created | 10 July 2019 — measured — dated from the channel’s first post |
| First recorded | 13 August 2026 |
| Last confirmed live | 16 August 2026 |
| Measurements held | 2 |
| On Telegram | t.me/bgorft |
Growth
| Measured (UTC) | Subscribers | Change |
|---|---|---|
| 13 Aug 2026, 23:16 | 2 | no change |
| 7 Aug 2026, 14:29 | 2 | first reading |
Engagement
14 posts held, back to 10 July 2019 — 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 pageof 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 14 posts for this entry, the most recent from 27 February 2026. An engagement rate over an empty window would be a number about nothing.
What this channel posts
- Photos
- 6
- Videos
- 2
- Links
- 1
Lifetime counters from Telegram’s own channel header, read 13 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.
- Video runtime
- 29s
- Average length
- 15s
Measured directly from 2 videos with a duration reading, out of the posts we hold for this channel — not this channel’s whole posting history, only the sample this register has actually read. An exact reading to the second, taken from the post itself rather than from Telegram’s own rounded chrome, so it carries no ≈ mark.
Recent posts
18 Feb 2026, 19:39 UTC28 viewsread 13 August 2026
Video
Video, posted without a caption
31 Dec 2025, 12:19 UTC35 viewsread 13 August 2026
Forwarded from @media_rarePhoto
Шел 2026 год, Space X выходит на биржу с капитализацией триллион, спутниковый интернет покрыл планету, наши цифровые аватары фолловят друг друга в тиктоке, AGI скоро завоюет человечество.. ..а мы с поддержкой телеком оператора выбираем как доставить eSIM - ПОЧТОЙ или КУРЬЕРОМ. ЭЛЕКТРОННУЮ блин симкарту!! @media_rare
25 Dec 2025, 12:41 UTC28 viewsread 13 August 2026
Photo
Это не быстро деньги или u name it, это матьего Сплит от Яндекса, вместе с кодом подтверждения покупки изменил ставку по кредиту почти х2. Поддержка многократно ответила, что мол сам виноват, надо смотреть внимательнее. SHAME ON YOU!
10 Sept 2025, 08:27 UTC35 viewsread 13 August 2026
Photo
Ребята сделали работу над ошибками @delimobil 👍
23 Aug 2025, 11:34 UTC39 viewsread 13 August 2026
Photo
Когда говорят о продуктовой культуре, можно привести в пример, как не надо проектировать коммуникацию с пользователями @delimobil
7 May 2025, 17:21 UTC111 viewsread 13 August 2026
Video
да, это снег
28 Apr 2025, 14:19 UTC107 viewsread 13 August 2026
Photo
Photo, posted without a caption
26 Apr 2025, 19:14 UTC121 viewsread 13 August 2026
Forwarded from @forbesrussia
Вежливость пользователей чат-ботов, которые пишут в запросах «пожалуйста» и «спасибо», обходится компаниями в десятки миллионов долларов, заявил гендиректор OpenAI Сэм Альтман. Это объясняется тем, что добавление новых слов требует дополнительных вычислений. Вместе с тем некоторые исследователи отмечают важность соблюдения этикета при общении с чат-ботами, поскольку они обучаются на запросах пользователей
26 Apr 2025, 19:14 UTC92 viewsread 13 August 2026
Так же работает и с мозгом, если вы читаете всякую … или текст, залитый водой — просто тратите на это ресурс, который мог пойти на важное 👇
12 Jul 2024, 10:44 UTCviews —
Channel photo updated
12 Jul 2024, 09:45 UTC131 viewsread 13 August 2026
+1
Showing the 12 most recent of 14 posts we hold for @bgorft. 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
Republishes
Channels on the register whose posts this channel has forwarded.
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.
Mentions
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 13 August 2026 — this entry's latest reading, not the date you are reading this.
“BugOrFeature 💭” (@bgorft), 2 subscribers as measured 13 August 2026. Telegram Register, tgregister.com/channel/bgorft.
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.