Telegram RegisterThe public register of Telegram
Telegram profile photo for Гелик | Гелендваген

Channel

Гелик | Гелендваген

@Gelik60

On this record: Growth · Engagement · What this channel posts · Reactions · Advertising · Posts · Citations · Telegram's recommendations · Cite this entry

863subscribers

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

Register entry

Telegram ID-1001422236290
TypeChannel
Username@Gelik60
Description#мерседес #gelik #mercedes #mersedes #AMG #гелик #гелендваген #G63
CreatedBetween 1 April 2019 and 31 October 2021 — estimated from Telegram’s id allocation, not measured. How this range is calculated.
First recorded8 September 2026
Last confirmed live8 September 2026
Measurements held1
On Telegramt.me/Gelik60

Growth

Growth history is still building. We hold one measurement for this entry. A trend needs at least two, taken days apart — so this will fill in on its own rather than being estimated. We do not publish numbers we have not measured.

Measurement log — every subscribers count we have recorded
Measured (UTC)SubscribersChange
8 Sept 2026, 07:22863first reading

Engagement

19 posts held, back to 1 August 2024the 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 19 posts for this entry, the most recent from 27 April 2026. An engagement rate over an empty window would be a number about nothing.

What this channel posts

Photos
39
Videos
21
Links
2

Lifetime counters from Telegram’s own channel header, read 8 September 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
2m 33s
Average length
38s

Measured directly from 4 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.

Reaction mix

499 reactions across 19 posts, in 9 distinct kinds. The most used accounts for 54.9% of them.

Every reaction kind recorded on the sample, most used first
ReactionCountShareShare, drawn
👍27454.9%
🔥9619.2%
6713.4%
🥰346.81%
🖕122.40%
👎112.20%
👏30.601%
10.2%
💋10.2%

No sentiment is inferred, and none should be read in. This table is ordered by count and by nothing else. Emoji do not carry stable meaning across languages or communities — 🙏 is thanks in one channel and mourning in another — so we publish which ones were pressed and how often, and pass no judgement on what an audience meant by them.

Precision. Telegram publishes reaction counts per emoji and short-forms each one — 4.34K, 1.2M — so any single kind at or above 1,000 reaches us at three significant figures, and only counts below 1,000 are exact. The shares above are ratios of those figures and carry the same error. This is also why the total here can differ slightly from a reaction total printed elsewhere on the page: both are sums of the same rounded parts, taken over samples with different edges.

Coverage. Reactions were read on 19 of the 19 sampled posts in this sample. Summed by Telegram’s own count on each post — not by adding up the per-emoji breakdown above — those same posts carry 499 reactions in total: the kind of figure the paragraph above means by “a reaction total printed elsewhere on the page”.

Measured over the 19 most recent posts we hold, published 1 August 2024 to 27 April 2026, using the newest reading held for each. Telegram Stars are excluded: they are a payment, not a reaction, and they have their own section.

Advertising

Ad load
5.26%
1 of 19 posts carry an ad marker
Regulatory tokens
1
posts carrying an erid · 1 distinct token
Median views · ads
253
over 1 measured post
Median views · rest
778
over 18 measured posts

An ad marker, not a judgement about a post. A post is counted here because it carries one of two explicit markings: an erid token, which Russian law has required on paid placements since 2022 and which is issued against a specific advertising contract, or a #реклама / #ad hashtag in the body, which is the channel declaring it itself. The first is documentary; the second is a self-declaration and is weaker. No classifier reads the text and decides — nothing on this site guesses that a post is an advertisement.

This is a floor, and it can only ever be a floor. A channel that runs paid placements without marking them produces no marker for us to count, and an unmarked ad is indistinguishable from an ordinary post on the public surface. The ad load above therefore means “the share of posts that declared themselves”, never “the share of posts that were paid for”. A low figure is not evidence of a channel that runs few ads.

Both figures are medians, and no ratio between them is published. Each is a view reading that actually occurred on a post, picked by percentile_disc rather than averaged, so one viral post cannot move it and no interpolated value is invented between two readings. The sample on one side is under five posts, which is too thin to compare. The two figures are shown side by side with the count behind each, and deliberately not divided into a headline like “ads get x% fewer views” — an arithmetic that is easy to print and, at this sample size, means nothing.

Advertising tokens recorded on this entry
eridPostsFirst seenLast seen
2VtzquhKi6c116 November 202516 November 2025

A token repeated across several posts is one advertising contract placed more than once, which is what the identifier is for. The strings are reproduced exactly as they appeared in the post or in its click-through URL and are not validated against any registry — we record the marker a channel published, and whether it resolves to a real contract is a question for the register that issued it.

Measured over the 19 most recent posts we hold, published 1 August 2024 to 27 April 2026. Views are the latest single reading held for each post, and any reading at or above 1,000 is rounded by Telegram to three significant figures.

Recent posts

27 Apr 2026, 15:27 UTC100 views1 reactionsread 8 September 2026

💬 Плохо грузит Telegram? Заходи в наш MAX 👉 Подписаться

👍1

16 Nov 2025, 17:30 UTC253 views5 reactionsread 8 September 2026
Advertisementerid 2VtzquhKi6cPhoto

Запариватель, достойный Пушкина. Классика надёжности в современной оболочке! Знаете, где впитывал энергию наш запариватель из тайвека? В Тифлисских банях — там, где бывал сам Александр Сергеевич. Переходи в канал и ознакомься с уникальным и первым в своём роде аксессуаром для банных процедур. https://t.me/Poshli_Paritsya?erid=2VtzquhKi6c

👍5

22 Aug 2025, 11:27 UTC272 views6 reactionsread 8 September 2026
Video

В России обнаружили «гелики» за 337.000₽, но есть нюанс.

👍6

7 Jul 2025, 17:59 UTC321 views8 reactionsread 8 September 2026
Video

#Мерседес #гелик #Gelik🖤🔥

🔥6👍2

9 May 2025, 21:11 UTC389 views8 reactionsread 8 September 2026
Video

#Мерседес #гелик #Gelik🖤🔥

4🔥3👍1

26 Feb 2025, 21:39 UTC579 views11 reactionsread 8 September 2026
Photo

#мерседес 🔥❤️‍🔥

👍4🥰43

25 Dec 2024, 14:48 UTC550 views10 reactionsread 8 September 2026
Forwarded from @mersedes_cls1Photo

#Мерседес 😍🔥

👍82

30 Nov 2024, 02:47 UTC≈1,080 views7 reactionsread 8 September 2026
Photo

#Мерседес #Гелик🔥🖤

👍43

15 Nov 2024, 16:10 UTC778 views10 reactionsread 8 September 2026
Forwarded from @mersedes_cls1Photo

Красотка🖤😍 #Мерседес #CLS63

👍53🔥2

10 Nov 2024, 20:51 UTC923 views8 reactionsread 8 September 2026
Photo

#Мерседес #Гелик🔥🖤

👍61🔥1

Showing the 12 most recent of 19 posts we hold for @Gelik60. 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.

Appears in Telegram’s recommendations for other channels

The reverse of the list above, and a different kind of signal. This does not require this channel to have ever been asked about directly — each row below is a channel we DID ask Telegram about, whose Telegram-generated list happened to include this one. A channel can appear here with an empty list above it, because being named by someone else’s query is independent of having been queried itself.

Русские хиты | Музыка | Песни
@khity2 · 29,583
Telegram ranks this channel #56 of 85 here — alongside 84 others — read 8 September 2026

This channel appears in 1 seed channel's Telegram-generated recommendation list in total. Each is Telegram’s list for THAT channel, not this one — see how this is measured.

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.

“Гелик | Гелендваген” (@Gelik60), 863 subscribers as measured 8 September 2026. Telegram Register, tgregister.com/channel/Gelik60.

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.