en
Feedback
LegendDiary 0.2

LegendDiary 0.2

Open in Telegram

📈 Analytical overview of Telegram channel LegendDiary 0.2

Channel LegendDiary 0.2 (@legenddiary02) in the Burmese language segment is an active participant. Currently, the community unites 15 124 subscribers, ranking 49 246 in the Erotic category and 6 599 in the Myanmar region.

📊 Audience metrics and dynamics

Since its creation on невідомо, the project has demonstrated rapid growth, gathering an audience of 15 124 subscribers.

According to the latest data from 08 September, 2024, the channel demonstrates stable activity. Although there has been a change in the number of participants by 0 over the last 30 days and by 0 over the last 24 hours, overall reach remains high.

  • Verification status: Not verified
  • Engagement rate (ER): The average audience engagement rate is 0%. Within the first 24 hours after publication, content typically collects N/A% reactions from the total number of subscribers.
  • Post reach: On average, each post receives 0 views. Within the first day, a publication typically gains 0 views.
  • Reactions and interaction: The audience actively supports content: the average number of reactions per post is 0.

📝 Description and content policy

Channel description not provided.

Thanks to the high frequency of updates (latest data received on 09 September, 2024), the channel maintains relevance and a high level of publication reach. Analytics show that the audience actively interacts with content, making it an important point of influence in the Erotic category.

15 124
Subscribers
No data24 hours
No data7 days
No data30 days

Data loading in progress...

Attracting Subscribers
May '24
May '24
+3
in 0 channels
April '24
+2 206
in 2 channels
Get PRO
March '24
+2 665
in 1 channels
Get PRO
February '24
+3 312
in 4 channels
Get PRO
January '24
+2 413
in 3 channels
Get PRO
December '23
+2 702
in 2 channels
Get PRO
November '23
+3 019
in 1 channels
Date
Subscriber Growth
Mentions
Channels
01 May+3
Channel Posts
No data
Any problems? Please refresh the page or contact our support manager.