Update: 25/10/2024
25 – 26 October (+ about 24h LCI).
Info about live statistics is at the bottom, below the tables.
Basic info:
- If someone is watching from the phone, it’s best to hold your phone horizontally (or scroll the tables horizontally)
- All tables are pageable, sortable, and filterable ('search').
- All dates and times in the tables are shown in DD/MM/YYYY format, in local festival time (unless stated otherwise)
- With a large number of checkins / people / beers, there may be some delays in updating, discrepancies between the tables (especially at the beginning of the festival), which will level out after some time. Plus, there will probably be unloaded pictures - that will take time, because pics have a lower priority than check-ins.
- In this context, 'live' means 'every few minutes' - but see above - the beginning of major festivals can be challenging
- UT accounts hidden by users are not included in the statistics
- Only checkins that have monitored venue marked as "Location" are taken into account ("Purchased Location" is not enough). Which venues are monitored can be seen in the first table
- The tables on the page do not refresh automatically - you will have to reload the page in your browser if necessary.
- Edits on UT made with a delay are taken into account live only for a few / tens of seconds, but not selecting a venue and adding it later, or changing a beer or rating will be included with a delay (limited to last 300 checkins per user)
- If you use a third party application (e.g. jonpacker.com for MBCC), you may be skipped (workaround: do the first check-in normally, with UT and sync data between the third-party app and UT every 200-250 check-ins). UPD: Since UT changed their API policy, this potential problem seems to be fading away, as there’s a good chance all similar 3rd party apps are disappearing too.
- If you don't show up in the stats, make sure you don't have a hidden account or "shadow-ban" - especially check if your checkins are visible on the venue's page.
- Top3 columns in the tables do not recognize ties - always only 3 positions, if there are ties in values, the order is determined chronologically. Also, for top3 ratings, a minimum of 3 ratings is required to be included.
- The "Fest. Hate / Hype" column is the difference between the UT arithmetic average (at the moment of the first checkin at the festival, without subsequent updates) and the arithmetic average of ratings at the festival. If the beer did not have an UT average on the start of festival, the Hate / Hype is 0.
- If you don't know what Bayesian average is, I invite you >>here<< (unfortunately in Polish, but with pics & links to english language pages)
- There are (as per Brewer Stage) minimum number of checkins for beers and breweries to be included in the tables. You can see the required numbers in the first table with parameters or on that chart
- "Wght. Avg (from Bayes)" in the Breweries table is calculated for all beers, even those that don’t meet the minimum check-in requirement.
- Backlogs / late check-ins will be collected about a day after the end of the festival
- The tables will be trimmed if their data exceeds 2 MB (applies only to exceptional cases / largest festivals and only to tables of users and beers. 2 MB = about 4K users or 2K Beers).
- Remember - the fact that a beer has a low rating does not mean that it is bad, but only that some other people did not like it. You may have different taste 🙂
- If anything’s unclear, you have questions, spot any mistakes, or - for example - want another festival included -> feel free to reach out (FB Messenger:
Rami Ramidus). - I hope that nothing will fail (it works on an old laptop at home), but anyway: I do not take responsibility for anything (in particular: for the correctness of data), and I wish you nice statistics :>
