Telegram RegisterThe public register of Telegram
Telegram profile photo for 𖥻𝐋𝐀𝐕«🪻»𝐆𝐀𝐑˙˖໑˳⤸ info

Channel

𖥻𝐋𝐀𝐕«🪻»𝐆𝐀𝐑˙˖໑˳⤸ info

@lav_gar_info

On this record: Growth · Engagement · What this channel posts · Reactions · Posts · Citations · Handles named that no longer answer · Cite this entry

3subscribers

+0 since we began measuring on 14 August 2026

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

Register entry

Telegram ID-1001804913617
TypeChannel
Username@lav_gar_info
CreatedBetween 1 October 2022 and 26 August 2023— estimated from Telegram’s id allocation, not measured. How this range is calculated.
First recorded14 August 2026
Last confirmed live15 August 2026
Measurements held2
On Telegramt.me/lav_gar_info

Growth

314 Aug 2026, 19:07 — 3 subscribers14 Aug 2026, 19:32 — 3 subscribers14 Aug 2026, 19:0714 Aug 2026, 19:32
2 measurements taken within a single day. 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 2–4 and does not start at zero.
Measurement log — every subscribers count we have recorded
Measured (UTC)SubscribersChange
14 Aug 2026, 19:323no change
14 Aug 2026, 19:073first reading

Engagement

12 posts held, back to 26 August 2023the 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 12 posts for this entry, the most recent from 23 October 2024. An engagement rate over an empty window would be a number about nothing.

What this channel posts

Photos
32
Videos
2
Links
8

Lifetime counters from Telegram’s own channel header, read 14 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
28s
Average length
28s

Measured directly from 1 video 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

12 reactions across 7 posts, in 5 distinct kinds. The most used accounts for 33.3% of them.

Every reaction kind recorded on the sample, most used first
ReactionCountShareShare, drawn
👍433.3%
💘433.3%
❤‍🔥216.7%
😁18.33%
🥰18.33%

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 7 of the 12 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 12reactions in total: the kind of figure the paragraph above means by “a reaction total printed elsewhere on the page”.

Measured over the 12 most recent posts we hold, published 26 August 2023 to 23 October 2024, using the newest reading held for each. Telegram Stars are excluded: they are a payment, not a reaction, and they have their own section.

Recent posts

23 Oct 2024, 10:57 UTC121 viewsread 14 August 2026
Photo

𝁨 𝖲𝗁𝖾 𝗂𝗌 𝗆𝗈𝗋𝖾 𝖻𝖾𝖺𝗎𝗍𝗂𝖿𝗎𝗅 𝗍𝗁𝖺𝗇 𝖬𝖺𝗒, 𝗆𝗈𝗋𝖾 𝖻𝖾𝖺𝗎𝗍𝗂𝖿𝗎𝗅 𝗍𝗁𝖺𝗇 𝗍𝗁𝖾 𝗉𝖾𝗍𝖺𝗅𝗌 𝗈𝖿 𝗉𝖺𝗋𝖺𝖽𝗂𝗌𝖾. 𝖬𝗒 𝗍𝖾𝗇𝖽𝖾𝗋 𝖫𝖺𝗏𝖾𝗇𝖽𝖾𝗋 𝗀𝖺𝗋𝖽𝖾𝗇, 𝗂𝗅𝗅𝗎𝗆𝗂𝗇𝖺𝗍𝖾𝖽 𝖻𝗒 𝖺 𝖽𝗂𝗆 𝗅𝖺𝗇𝗍𝖾𝗋𝗇. ───── “𝐋𐐼𝗏𝖺𝗇𝖽𝖾𝗋 𝗀𝖺𝗋𝖽ꫀ𝗇” › ›🎥`𝖨 𝐩𝐫: 𝖼𝗁𝖺𝗍 & 𖥻 𝗁.𝗍𝖺𝗀𝗌: ( ⭑ )) 𝖵𝖺𝗋𝗂𝗈𝗎𝗌 𝖿𝖺𝗇𝖽𝗈𝗆 𝗌𝗍𝗂𝖼𝗄𝖾𝗋𝗌, 𝗁𝗂𝗀𝗁-𝗊𝗎𝖺𝗅𝗂𝗍𝗒 𝗉𝗈𝗌𝗍𝗌 𝖺𝗇𝖽 𝖾𝖽𝗂𝗍𝗌 𝗐𝗂𝗍𝗁 𝗒𝗈𝗎𝗋 𝖿𝖺𝗏𝗈𝗋𝗂𝗍𝖾 𝖼𝗁𝖺𝗋𝖺𝖼𝗍𝖾𝗋𝗌! 𝖨𝗇 𝗈𝗎𝗋 𝖼𝗈𝗓𝗒 𝖼𝗈𝗋𝗇𝖾𝗋! ☆..

23 Oct 2024, 10:57 UTC139 viewsread 14 August 2026
Photo

───────── · ·𝐀𝐧𝐝𝐢 𝐦𝐢𝐧𝐧 𝐬𝐞𝐫 𝐢 𝐠𝐞𝐠𝐧 ׅ ׁ ‧⭑ ‹𝐋𐐼𝗏𝖺𝗇𝖽𝖾𝗋 𝗀𝖺𝗋𝖽ꫀ𝗇· · •

23 Oct 2024, 10:57 UTC114 viewsread 14 August 2026
Photo

────── · · •𝐈𝐧 𝐡𝐚𝐜 𝐧𝐨𝐜𝐭𝐞, 𝐥𝐮𝐜𝐫𝐮𝐦 𝐯𝐢𝐫𝐭𝐮𝐬 ׅ ׁ ‧⭑ ‹𝐋𐐼𝗏𝖺𝗇𝖽𝖾𝗋 𝗀𝖺𝗋𝖽ꫀ𝗇· · •

14 Aug 2024, 16:56 UTC156 viewsread 14 August 2026
Forwarded from @LAVGARPhoto

Пиздати ап на @ACRUXSL 13 августа, примерно в 8 вечера по мск я увидела объявление о продаже пиар-чата. Но подумала, что его уже продали, поэтому стала искать похожие объявления, выяснилось, то что данная особа понизила цену с 130к рдно до 40к рдно за пч. Мне стало жалко и я решила заплатить 80к рдно(скрины сделки прикрепила). Когда зашла в пч, мы поняли, то что она не может передать права, сможет только через неделю

1 Feb 2024, 08:23 UTC269 viewsread 14 August 2026
Forwarded from @LAVGARPhoto

АП НА @stafmii владелец этого канала (@liristix) своровал работу нашего админа. В обсуждении канала мы увидели такое сообщение https://t.me/lavender_gardens_com/30041. Человек сказал, что нашу работу украли и прикрепил эту сс, это была ссылка на сам пост, который на втором скрине. Обратите внимание на работы. 1 скрин - наша, 2 скрин - его "работа". Также посмотрите время отправки. Наша работа намного раньше была отп

23 Dec 2023, 11:29 UTC≈4,220 views5 reactionsread 14 August 2026
Photo

🪻 ⲃⲁⲙ ⲡⲣυⲱⲗⲟ ⲡυⲥьⲙⲟ ⲡⲣυⲅⲗⲁⲱⲉⲏυⲉ ⲃ ⲏⲉⲟⳝыⳡⲏⲟⲉ ⲙⲉⲥⲧⲟ🪻 нᥱ жᥱ᧘ᥲᥱᴛᥱ ᥰρ᧐ᴦу᧘яᴛьᥴя ᥰ᧐ ᧘ᥲʙᥲнд᧐ʙ᧐ⲙу ᥴᥲду? уʙᥱρяю Вᥲᥴ, ᥴᥲд ᥙ ᥱᴦ᧐ ᧐δᥙᴛᥲᴛᥱ᧘ᥙ δудуᴛ ρᥲд ᥴᴛ᧐᧘ь ᥰρᥱκρᥲᥴн᧐ⲙу ᴦ᧐ᥴᴛю. нᥲдᥱюᥴь ᥴᥲд ᤋᥲчᥲρуᥱᴛ Вᥲᥴ ᥴʙ᧐ᥱᥔ κρᥲᥴ᧐ᴛ᧐ᥔ ᥙ Вы ᥰρᥙᥴ᧐ᥱдᥙнᥙᴛᥱᥴь κ ᥱᴦ᧐ жᥙᴛᥱ᧘яⲙ. @ⲏⲉυⳅⲃⲉⲥⲧⲏыύ ⲟⲧⲡⲣⲁⲃυⲧⲉⲗь

💘2👍1🥰1😁1

26 Aug 2023, 22:50 UTC349 views1 reactionsread 14 August 2026
Forwarded from @LAVGAR

#𝐉𝐨𝐬𝐞𝐩𝐡 мы дополнили это заявление. И помимо извинений перед @Ewokia за неосторожное внесение список спамеров, объяснили ПРИЧИНУ возникновение данной ошибки. Все ДОКАЗАТЕЛЬСТВА так же есть в коммах под данным постом. А так же в этом посту мы показали всю ситуацию без обмана, превратив его в "ап" в сторону @Mak_kli . Так как она нехило наехала на нас. Надеюсь такие ужасные инциденты не возникнут ни у кого на этом све

👍1

26 Aug 2023, 22:50 UTC301 views2 reactionsread 14 August 2026
Forwarded from @LAVGAR

#𝐉𝐨𝐬𝐞𝐩𝐡 Я закрыл коммы. Кто попало писать не смогут. И за любое оскорбление и хейт БАН И КИК. Я сыт по горлу негативом в адрес моих админов и участников рп. Я никому не позволю лезть к ним. УЯСНИЛИ? и вообще.. ВАМ НЕ КУДА ТРАТИТЬ СВОЮ ЗЛОБУ? Так идите вымещать её на других. Не зачем к моим ребятам лезть. Меня уже искренний заебало то что у многих нету глаз чтобы прочесть ПРАВИЛА, и нету мозгов чтобы не создавать сума

👍1💘1

26 Aug 2023, 22:50 UTC275 views1 reactionsread 14 August 2026
Forwarded from @LAVGAR

Приносим извинения в сторону @Ewokia Данный человек был удалён из группы в связи с нарушением правил и оскорбления администрации. Он буквально обзывал администрацию и участников ролевой. ⬇️ и ДОКАЗАТЕЛЬСТВО ЭТОМУ вы можете найти в комментариях под этим постом.⬇️ В связи с достаточно шадким состоянием нами была допущена ошибка, в связи с которой мы случайно добавили его в список спамеров. На данный момент мы уже убрал

👍1

26 Aug 2023, 20:54 UTC279 views1 reactionsread 14 August 2026
Forwarded from @LAVGARPhoto

— ночью 25.08 в 00:36 по московскому времени в чате ролевой канала @lavender_gardens произошёл спам. Один из бывших участников ролевой который был удалён вместе со своими друзьями из ролевой по причине оскорблений, и нарушений прописанных правил слил ссылку на чат рп [ флуд является частным, из-за чего слить его попросту не получилось ]. Спамщиками являются непосредственно данные личности[на видео видно то как те спа

❤‍🔥1

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

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

“𖥻𝐋𝐀𝐕«🪻»𝐆𝐀𝐑˙˖໑˳⤸ info” (@lav_gar_info), 3 subscribers as measured 14 August 2026. Telegram Register, tgregister.com/channel/lav_gar_info.

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.