Telegram RegisterThe public register of Telegram
Telegram profile photo for ليكُن لِقاء

Channel

ليكُن لِقاء

@l227e

Not marked by Telegram, checked 27 August 2026

On this record: Topic · Growth · Engagement · Posts · Telegram's recommendations · Cite this entry

1,062subscribers

-20 since we began measuring on 26 August 2026

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

Register entry

Telegram ID-1002211569945
TypeChannel
Username@l227e
CreatedBetween 1 June 2024 and 30 September 2024 — estimated from Telegram’s id allocation, not measured. How this range is calculated.
First recorded26 August 2026
Last confirmed live25 October 2026
Measurements held14
Confirmed unchanged2 times, most recently 25 October 2026
On Telegramt.me/l227e

Topic

Other / unclassifiable — 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 19 September 2026 and assigned it the closest of 31 fixed categories, at 58% 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,0621,0901,07626 August 2026 — 1,082 subscribers26 August 2026 — 1,081 subscribers29 August 2026 — 1,082 subscribers1 September 2026 — 1,081 subscribers6 September 2026 — 1,086 subscribers10 September 2026 — 1,089 subscribers14 September 2026 — 1,090 subscribers19 September 2026 — 1,079 subscribers29 September 2026 — 1,083 subscribers6 October 2026 — 1,074 subscribers13 October 2026 — 1,071 subscribers15 October 2026 — 1,068 subscribers18 October 2026 — 1,069 subscribers22 October 2026 — 1,062 subscribers26 August 202622 October 2026
14 measurements spanning 57 days, net -20. 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,058–1,094 and does not start at zero.
Measurement log — every subscribers count we have recorded
Measured (UTC)SubscribersChange
22 Oct 2026, 06:311,062-7
18 Oct 2026, 17:061,069+1
15 Oct 2026, 19:471,068-3
13 Oct 2026, 00:461,071-3
6 Oct 2026, 16:391,074-9
29 Sept 2026, 07:381,083+4
19 Sept 2026, 00:561,079-11
14 Sept 2026, 09:361,090+1
10 Sept 2026, 19:191,089+3
6 Sept 2026, 02:381,086+5
1 Sept 2026, 23:461,081-1
29 Aug 2026, 19:121,082+1
26 Aug 2026, 22:241,081-1
26 Aug 2026, 02:011,082first reading

Engagement

18 posts held, back to 5 July 2026 — the 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 18 posts for this entry, the most recent from 23 August 2026. An engagement rate over an empty window would be a number about nothing.

Recent posts

23 Aug 2026, 23:07 UTC102 viewsread 26 August 2026

أحبك من چنت ما تطلع الباب وكرهـتك من لكيتك ب الدرابين .

23 Aug 2026, 23:07 UTC102 viewsread 26 August 2026

چنت وياك صدكي بكل الحچايات وچنت وياي حتى بدمعك تچذب .

23 Aug 2026, 23:07 UTC101 viewsread 26 August 2026

أكل عمري الحزن واستفحل الشيب مثل سبورة تاكل بالطباشير .

23 Aug 2026, 23:07 UTC102 viewsread 26 August 2026

مـو بخلن عليك وشنهي العيون بس لو اخذت عيني بيش اشوفك .

23 Aug 2026, 23:07 UTC101 viewsread 26 August 2026

فراغك والكبر يشابهن حيل منو المنهن يعيش بروحي وصيته .

23 Aug 2026, 23:07 UTC100 viewsread 26 August 2026

فرق بين اليحطلي على الدرب عثرات وفرق بين العثر وياي من اعثر .

13 Aug 2026, 22:05 UTC293 viewsread 26 August 2026
Photo

أتمنى أن تكون دائماً بقربي❤️.

Signed h.

2 Aug 2026, 22:03 UTC489 viewsread 26 August 2026

هوآي عتبوَا ع المّحطة وهم يوُميه بقطار ؟.

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

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.

مُنمَّق
@MJJJI · 28,222
Telegram ranks this channel #31 of 71 here — alongside 70 others — read 9 September 2026
-نَرجسّيه.
@Ssll_77 · 47,338
Telegram ranks this channel #47 of 78 here — alongside 77 others — read 26 August 2026

This channel appears in 2 seed channels' Telegram-generated recommendation lists 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 22 October 2026 — this entry's latest reading, not the date you are reading this.

“ليكُن لِقاء” (@l227e), 1,062 subscribers as measured 22 October 2026. Telegram Register, tgregister.com/channel/l227e.

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.