← All sources
DailyLive-testedOfficial public-page backend
Justice / Court schedules
Tbilisi Court of Appeals daily hearing schedule
Official same-day hearing table for the Tbilisi Court of Appeals, listing date, time, courtroom, judge, and parties. It is operational and current but ephemeral, unstructured, and privacy-sensitive.
01
Provenance and access
How the data is reached
Unauthenticated HTML table. On 22 July 2026 the page showed a 22-07-2026 schedule with 27 data rows (28 tr elements including the header).
Reuse status
Unclear; judicial publicity does not itself establish an open-data reuse license
Daily schedule page
https://tbappeal.court.ge/en/page/ganrigi ↗- Method
- GET
- Format
- HTML
- Authentication
- None observed
The same route appears to be overwritten with the current schedule.
02
Field-level detail
What is actually returned
livereferencederivedhistoricalunknown
Scheduled hearing row
One row in the public schedule table.
| Field / path | Type | Null? | Example | Meaning | Freshness |
|---|---|---|---|---|---|
date | date string | No | 22.07.2026 | Hearing date | live |
time | time string | No | [HH:MM] | Scheduled local start time | live |
courtroom | string | No | №1 | Courtroom number/label | live |
judge | string | No | [name omitted] | Assigned judge | live |
parties | string | No | სსიპ სახელმწიფო ქონების ეროვნული სააგენტო, შპს „გრომ 001“ | Named case parties as published | live |
03
Representative evidence
Sample records
Organization-only hearing row
Retrieved 2026-07-22T13:56:00+04:00
date=22.07.2026; courtroom=№1; parties=სსიპ სახელმწიფო ქონების ეროვნული სააგენტო, შპს „გრომ 001“; time and judge omitted from sample; natural-person rows omitted04
Boundaries
Reliability, caveats, and privacy
What held up
- The official page returned HTTP 200
- The displayed date matched the retrieval date
- Table headers and 27 data rows were directly counted
What can go wrong
- Schedules can change after retrieval
- No stable case ID is displayed in the table
- The route is likely ephemeral and should not be assumed to provide history
- Published data contains formatting anomalies and inconsistent masking
- Court publicity is not permission for bulk profiling
Privacy boundary
- Many rows expose natural-person party names. Avoid bulk indexing, re-identification, sensitive-case inference, or joining against other person-level data; minimize retention and prefer organization-only examples.
05
Cross-source possibilities
Ideas using this source
06
Source trail
Primary pages and documentation
https://tbappeal.court.ge/en/page/ganrigi