Telegram RegisterThe public register of Telegram
Telegram profile photo for WebDev

Channel

WebDev

@rikideveloper

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

7subscribers

+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-1001728078650
TypeChannel
Username@rikideveloper
Created13 November 2021measured — dated from the channel’s first post
First recorded12 August 2026
Last confirmed live13 August 2026
Measurements held2
On Telegramt.me/rikideveloper

Growth

77 August 2026 — 7 subscribers12 August 2026 — 7 subscribers7 August 202612 August 2026
2 measurements spanning 6 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 6–8 and does not start at zero.
Measurement log — every subscribers count we have recorded
Measured (UTC)SubscribersChange
12 Aug 2026, 16:197no change
7 Aug 2026, 01:347first reading

Engagement

4 posts held, back to 13 November 2021the 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 4 posts for this entry, the most recent from 12 April 2024. An engagement rate over an empty window would be a number about nothing.

Recent posts

12 Apr 2024, 21:05 UTC124 viewsread 12 August 2026
Forwarded from @seospecialist

Запощу одну важную вещь, которую я далеко не сразу понял, работая с аутсорсерами: При подготовке ТЗ (не важно кому) не стоит экономить время, чтобы как можно скорее отдать задачу в работу, вместо этого лучше максимально подробно 🧾 описать все, даже казалось бы незначительные нюансы, которые видятся очевидными, после чего на основе ТЗ организовать сессию вопрос/ответ - пройтись по каждому пункту, уточняя чего человек

13 Nov 2021, 10:27 UTC433 viewsread 12 August 2026

Занимаюсь разработкой всего что касается веба. Имею большой опыт в арбитраже трафика с разных источников, а именно доров, гугл адс+юак, фб, биржы трафика от старых и действующих топов до самых новых. Большой опыт работы с разными клоаками и решениями для клоакинга. Так же и с трекерами, предпочтение отдаю кейтаро. Владею яп python, symphony, node.js, typescript. Есть свой дизайнер который работает со мной в паре, по

Showing the 4 most recent of 4 posts we hold for @rikideveloper. 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 12 August 2026 — this entry's latest reading, not the date you are reading this.

“WebDev” (@rikideveloper), 7 subscribers as measured 12 August 2026. Telegram Register, tgregister.com/channel/rikideveloper.

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.