Telegram RegisterThe public register of Telegram
Telegram profile photo for Live hosting service

Supergroup

Live hosting service

@LiveServiceprovider

Has discussion group

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

1,145members

-48 since we began measuring on 11 August 2026

23 online right now

Risers and fallers across the register · movement among entries of 1,000–3,162.

Register entry

Telegram ID-1001550871022
TypeSupergroup
Username@LiveServiceprovider
CreatedBetween 1 August 2021 and 28 February 2023 — estimated from Telegram’s id allocation, not measured. How this range is calculated.
First recorded5 October 2026
Last confirmed live8 October 2026
Measurements held14
Confirmed unchanged1 time, most recently 8 October 2026
On Telegramt.me/LiveServiceprovider

Topic

Job listings — a classification, not a measurement. An on-box language model (Qwen3.6-35B-A3B-FP8, prompt version 1) read this channel’s own recent posts on 5 October 2026 and assigned it the closest of 31 fixed categories, at 96% confidence. This is a model’s judgement about what the channel is likely to be about, not a fact this register measured the way a subscriber count or a view count is measured — it can be revised on a later pass, and it carries no weight anywhere else on this page. How this classification works, and why it has no browse page of its own yet.

Growth

1,1451,1931,16911 August 2026 — 1,193 members12 August 2026 — 1,192 members16 August 2026 — 1,190 members22 August 2026 — 1,187 members25 August 2026 — 1,185 members28 August 2026 — 1,184 members31 August 2026 — 1,183 members3 September 2026 — 1,177 members9 September 2026 — 1,172 members13 September 2026 — 1,168 members16 September 2026 — 1,166 members1 October 2026 — 1,154 members5 October 2026 — 1,154 members8 October 2026 — 1,145 members11 August 20268 October 2026
14 measurements spanning 58 days, net -48. 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 1,138–1,200 and does not start at zero.
Measurement log — every members count we have recorded
Measured (UTC)MembersChange
8 Oct 2026, 10:181,145-9
5 Oct 2026, 17:451,154no change
1 Oct 2026, 11:541,154-12
16 Sept 2026, 13:391,166-2
13 Sept 2026, 00:381,168-4
9 Sept 2026, 03:351,172-5
3 Sept 2026, 22:211,177-6
31 Aug 2026, 15:551,183-1
28 Aug 2026, 09:171,184-1
25 Aug 2026, 19:131,185-2
22 Aug 2026, 09:531,187-3
16 Aug 2026, 08:381,190-2
12 Aug 2026, 10:151,192-1
11 Aug 2026, 13:471,193first reading

Engagement

Posts not read yet. This entry is on the register from its profile alone; the post reader has not reached it. Engagement figures appear here once posts have actually been measured — we do not publish a rate before we have the readings behind it.

Forward network

Republished by

Channels on the register that have forwarded this channel's posts into their own feed.

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.

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

“Live hosting service” (@LiveServiceprovider), 1,145 members as measured 8 October 2026. Telegram Register, tgregister.com/channel/LiveServiceprovider.

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.