Telegram RegisterThe public register of Telegram
Telegram profile photo for Locum.ru

Channel

Locum.ru

@locum

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

109subscribers

+2 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-1001008159044
TypeChannel
Username@locum
Created25 September 2015measured — dated from the channel’s first post
First recorded9 August 2026
Last confirmed live8 September 2026
Measurements held3
Confirmed unchanged1 time, most recently 8 September 2026
On Telegramt.me/locum

Growth

1071091087 August 2026 — 107 subscribers9 August 2026 — 107 subscribers8 September 2026 — 109 subscribers7 August 20268 September 2026
3 measurements spanning 32 days, net +2. 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 107–109 and does not start at zero.
Measurement log — every subscribers count we have recorded
Measured (UTC)SubscribersChange
8 Sept 2026, 09:55109+2
9 Aug 2026, 08:31107no change
7 Aug 2026, 19:01107first reading

Engagement

7 posts held, back to 25 September 2015the 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 7 posts for this entry, the most recent from 18 April 2018. An engagement rate over an empty window would be a number about nothing.

Recent posts

18 Apr 2018, 10:19 UTC≈17,300 viewsread 9 August 2026

Привет всем, кто тут остался. До конца недели напишите в заявке в саппорт секретное слово "Павел Дуров" и получите 500 руб бонусов на счёт хостинга.

5 Nov 2015, 22:19 UTC≈17,600 viewsread 9 August 2026

Друзья, мы тут случайно запустили очень хороший сервер под vds в Лондоне. Можно писать в поддержку и заказывать виртуальные машинки там. Цены такие же, как на сайте. Как и везде, честный KVM без оверселла, аппаратный рейд, правда, не SSD, но с хорошим кешем.

31 Oct 2015, 12:07 UTC≈17,500 viewsread 9 August 2026

Сегодня с 20:00 до полуночи остановим сервера БД mysql0, postgresql0, mongodb0 для большой профилактики и обновления версий баз данных. Постараемся закончить работы по возможности быстрее.

27 Oct 2015, 14:12 UTC≈14,000 viewsread 9 August 2026

Сегодня в 21:00 на 15 минут остановим сервера БД mysql0, postgresql0, mongodb0.

24 Oct 2015, 17:03 UTC≈8,220 viewsread 9 August 2026

В Joomla нашли очередную уязвимость, разработчики уже выпустили патч. http://www.opennet.ru/opennews/art.shtml?num=43186

7 Oct 2015, 14:15 UTC≈2,830 viewsread 9 August 2026

Сегодня с 22:30 до 23:30 для профилактики остановим mysql6, postgresql6, calcium, titanium. Меняем память, обновляем ядро.

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

“Locum.ru” (@locum), 109 subscribers as measured 8 September 2026. Telegram Register, tgregister.com/channel/locum.

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.