# Moderator Reading Time **URL:** https://meta.discourse.org/t/moderator-reading-time/121187 **Category:** Support **Created:** [June 24, 2019, 5:06pm UTC](https://meta.discourse.org/t/moderator-reading-time/121187 "2019-06-24T17:06:26Z") **Posts on this page:** 1 **Showing post:** 2
### Author: ![simon](https://sea3.discourse-cdn.com/meta/user_avatar/meta.discourse.org/simon/32/339122_2.png) [@simon](https://meta.discourse.org/u/simon) #### Post date: [June 25, 2019, 12:34am UTC](https://meta.discourse.org/t/moderator-reading-time/121187/2 "2019-06-25T00:34:39Z")
The short answer is that the Time Reading column in the Moderators activity report is caluculated by summing the values of the `time_read` field of the `user_visits` table for each of a site’s moderators over the report’s time period. The best description I’ve seen of how Discourse sets the value of the `time_read` field is in the **How the Discourse client tracks timing** section of this post: > [@How does post tracking work in Discourse](https://meta.discourse.org/t/how-does-post-tracking-work-in-discourse/115790): > > Discourse tracks read time for every post users see on the screen. This system has evolved over the years and I find I often need to refer back to the code to figure out how this works and why it exists. This post covers the painful technical details of the current implementation. How the Discourse client tracks timing Post timing tracking is implemented in [screen-track.js.es6](https://github.com/discourse/discourse/blob/a80c1f40111d6c56da10eefea91c9baa43b9f4b5/app/assets/javascripts/discourse/lib/screen-track.js.es6). This module is responsible for tracking how long a post has been on the screen and how long the topic has been on scr… --- _[View the full topic](https://meta.discourse.org/t/moderator-reading-time/121187)._