Rules & Working Guide

A simple client guide for using the result chart, managing backend entries, and understanding server-time result release.

Quick Explanation for New Clients

PlayBhagLaxmi is a result chart website. Users visit the home page, select a date range, and check the released chart rows. Old released records stay saved, so users can review previous charts from the Old Records page. Admin manages rows from the backend. The system can also fill missed rows through cron, but public users only see rows after the correct server release time.

Client-friendly summary: Admin can prepare the full day chart early, but users cannot see future results before time. The website and API both follow server time, so phone time, browser time, or VPN does not change what appears.

1How Users Use the Chart

Users do not need login. They only open the home page and check released results in the chart.

  • Open the home page.
  • Select Start Date and End Date.
  • Press Go to filter the chart.
  • Check the matching Date, Time, and XA-XJ values.
  • Open Old Records to review past released charts.
  • On mobile, scroll sideways to see all columns.

2How Results Become Visible

Each row has a release time. A result can be saved early in admin, but it stays hidden until server time reaches that row time.

  • Server timezone: Asia/Kolkata.
  • Phone, browser, and laptop time cannot unlock future rows.
  • VPN cannot change result release timing.
  • Frontend and API both hide unreleased rows.

Result Chart Format

The chart is read from left to right. Each time slot has one complete row.

Column Meaning User View
Date The result date saved by admin or cron. Displayed as day-month-year.
Time The scheduled result time for that row. Displayed only after the server release time has passed.
XA-XJ Ten informational number columns for the chart row. Visible after release; hidden before release.

User Example

Example: A user wants to check results for 13-07-2026.

  1. User opens the home page.
  2. User selects Start Date: 2026-07-13.
  3. User selects End Date: 2026-07-13.
  4. User presses Go.
  5. The website shows only rows already released by server time.
Date Time XA XB XC User Can See?
13-07-2026 09:00 AM XA15 XB32 XC49 Yes, after 09:00 AM server time
13-07-2026 11:59 PM XA99 XB99 XC99 No, hidden until 11:59 PM server time

Old Records Example

Example: A user wants to review older released records.

  1. User opens Old Records from the footer.
  2. User selects a past start date and end date.
  3. User presses Search Old Records.
  4. The page shows saved records for that date range only if those rows are already released.
  5. The page never shows future or pending rows.

3Backend Admin Management

Admin login is used to manage result rows, schedules, and missed result handling.

  • Open admin login: /login.php.
  • Login with the admin username and password.
  • Open Number Update to manage result rows.
  • Enter row id, date, time, and XA-XJ values.
  • Press Update to save or Delete to remove.

4Cron & Missed Result Handling

If admin misses a result entry, the cron service can create due rows automatically using the saved schedule or existing chart times.

  • cron_results.php checks server time.
  • It creates only rows whose release time has already passed.
  • Running it again is safe because existing rows are skipped.
  • Admin can run it from Run Cron Now in the result editor.

Admin Example: Fill a Future Result

Example: Admin wants to prepare the 11:59 PM result early.

  1. Admin opens /login.php and logs in.
  2. Admin opens Number Update.
  3. Admin enters Date: 2026-07-13 and Time: 11:59 PM.
  4. Admin fills values like XA99, XB99, XC99 up to XJ.
  5. Admin presses Update.
  6. The row is saved, but public users and API cannot see it before 11:59 PM server time.

API & Data Safety

The public API follows the same release rule as the front page. If a result is filled before time, it remains hidden from API response until server time reaches the release time.

GET /api_results.php
GET /api_results.php?startDate=2026-07-13&endDate=2026-07-13
  • No unreleased result values are sent by API.
  • API response includes server time and timezone for transparency.
  • Remote cron access should use a cron token.

Daily Management Checklist

Before Result Time

  • Login to admin panel.
  • Check schedule/time slots.
  • Prepare rows if needed.
  • Confirm date and time are correct.

After Result Time

  • Check frontend chart.
  • Check API if used by app or partner site.
  • Run cron if admin missed an entry.
  • Use admin list to verify released/pending rows.

Usage Rules

  • This chart is for informational, educational, testing, and entertainment display only.
  • Do not use this website for gambling, betting, wagering, deposits, prizes, or financial activity.
  • Do not treat chart values as advice, prediction, guarantee, or instruction.
  • Users are responsible for how they interpret any displayed information.