Huurre's Fanfiction Reading Log

Huurre - frost, rime, hoarfrost [email protected] Updates to my Fanfiction Reading Log

[huurrefanfictionreadinglog]

It is here! Version 2.0 of my fantastic Huurre's Fanfiction Reading Log!

What has changed? A lot!

Apps Scripts for doing some of the things for you, for example picking up fanfic's name and tag information from open fics in AO3. For more questions about this, especially relating scraping, please check my faq from my new website.

More comprehensive statistics with better logics.

For more detailed list of new features will be published here and in the website within next 30 hours because I'm already running late from the time I have given for the release. :'D

I have two versions of the file available:

Starting 2024: For anyone who has logged their reading during 2024 and wants to move their history from 2024 to this new file.

Huurre's Fanfiction Reading Log (starting 2024) (Ver 2.0 12/29/2024)

Starting 2025: For anyone who wants to start from the "clean table".

Huurre's Fanfiction Reading Log (starting 2025) (Ver 2.0 12/29/2024)

For full setup guide, please see the link below:

I've also set up Discord server for this. It is complete work in progress for now, but it is also in the place where you can suggest what direction to take it!

Check out the Huurre's Fanfiction Reading Log community on Discord – hang out with 3 other members and enjoy free voice and text chat.

And with any problems, don't hesitate to contact me!

Now, I'll let you see and look for the file. Have fun!

[huurrefanfictionreadinglog]

A workaround for the 525 error

AO3 has been quite slow this year, and right now, Huurre's Fanfiction Reading Log gives a 525 error from almost every fic. As a workaround, I got tipped in Discord that maybe Transformativeworks could work. I tested it quickly and it worked! You can always change the link to the AO3 link after running the script. :) This way, you should be able to get most of the fics handled by the script.

I might work on an automatic link changer if it seems that the problem continues, but right now, I am way too obsessed with my writing, sorry. :D I just returned to work full-time this week after last autumn's burnout and working half-time after it, so my time is even more limited, but hopefully I still have time to do other things too during the summer!

[huurrefanfictionreadinglog]

Formula to change the link automatically to Transformativeworks

AO3 works on and off with scripts and bots, so here's how to change the link automatically to Transformativeworks link and still keep the AO3 link:

In Fics tab, create a new column for example after column A (before the AO3 link column).

Add this formula to the new column B:

=IFERROR(HYPERLINK("https://archive.transformativeworks.org" & REGEXEXTRACT(C62, "https?://[^/]+(.*)")),"")

HOX! Tumblr has sometimes messed up with quotation marks. If the formula doesn't work, just replace them with "normal" (straight) quotation marks.

The C62 in that formula is what you need to change. It tells the formula where the original link is. For example, in this formula, I have added the additional column after column A, moving the AO3 links to column C. I'm on cell B62 (column B, row 62). If you add the new column somewhere else, just edit the column to the one that has the AO3 link and the cell to the same row as you have chosen.

After that, you can drag the formula to other cells in the same column by choosing the cell (outlined with blue) and grabbing the small blue dot and dragging it down (or up). The formula will generate Transformativeworks link automatically, and when running the script, you just need to choose the right cell. :)

Other news: I'm doing my best to get some bugs fixed, but I returned to work full-time at the start of June, and it has taken its toll. My biggest passion is writing, and it has taken pretty much all of my free time from the past how many months, and I would honestly need a lot more hours in my days to be able to do everything I want, so this is a slow process, but I'm working on it.

Talking about the log keeps me better in check, and thanks to the discussion in Discord this week, I've dug into some of the things which have been waiting for my attention. Also, I have (an unofficial and officially unsupported) script for handling multiple links at once in Discord, so join me and others there! Overall, it's the easiest place to reach me and most likely the place where you will get the fastest answer to anything. Join link: https://discord.gg/2CTuh3rQXG

[huurrefanfictionreadinglog]

A workaround for the 525 error

AO3 has been quite slow this year, and right now, Huurre's Fanfiction Reading Log gives a 525 error from almost every fic. As a workaround, I got tipped in Discord that maybe Transformativeworks could work. I tested it quickly and it worked! You can always change the link to the AO3 link after running the script. :) This way, you should be able to get most of the fics handled by the script.

I might work on an automatic link changer if it seems that the problem continues, but right now, I am way too obsessed with my writing, sorry. :D I just returned to work full-time this week after last autumn's burnout and working half-time after it, so my time is even more limited, but hopefully I still have time to do other things too during the summer!

[huurrefanfictionreadinglog]

525 error while running Fetch Data script

The Fetch Data script might give the error 525 message. That's something I can't do anything about; it's in AO3's end (more in AO3's Tumblr). Run the script again. It might take a few tries before it works.

Also, with higher rating fics, the old script now works at least some of the time. Every fic I tried today filled the fandom that was a problem earlier. I don't know why and how, but let's just take it as it is. :D

So! There might be slowness and error messages within the next few months, but they are on AO3's end. I will try to follow closely how the scripts are working, but since it is as it is, I'll work on version 2.1 a bit longer so I can get all the features I want in it.

[huurrefanfictionreadinglog]

First fix for Fetch data script

Find the blog post also from Huurreauthor.com. There is also a video on how to open the Apps Scripts, otherwise, the contents are the same.

A bit over a week full of work with this. Unfortunately, it's not completed yet, I have some confusing problems with getting Fandom from the AO3 link and it seems that the script is quite slow at the moment. I'm not sure if there's anything I can do about that, but I will try.

So, first things first, what are the changes generally from the previous when thinking about how the script works?

Mature, Explicit and Not Rated fanfics have gotten new HTML at some point. At least I think so, since the script has worked before that well for all open fics. New HTML has only the date of the last update/completed. It means that these fanfics will not have a Published date.

Since I am going to publish the complete bug fix hopefully within the next two weeks, the script has only one Fetch Data script that has fandoms mentioned in the tags. This is just to make my work easier at the moment. :)

The script doesn't fetch Fandom at the moment. This is the main thing I'm going to fix with the next update. I'm pretty sure the fault lies in me with this as I couldn't get it to work, but a bit more time will help.

Popup when the fanfic is locked! This is a really good thing. I've got a message a few times that the script didn't do anything and then soon afterwards "Whoops, it was actually locked". Now that popup will tell you that the fic is locked and you have to fill in the information manually.

Lower rating fics are handled the same as previously, no changes there.

How to fix the script?

To make everything easier, I have downloaded the whole script to Google Drive where you can copy the whole code and replace the old code with it.

1. Open your file.

2. Choose Extensions > Apps Script from the top.

It opens a new window which can be a bit overwhelming at first.

3. Choose custom menu.gs from the left side panel.

4. Delete everything from that script.

5. Go to Google Drive through this link. Copy everything. (F.e. CTRL/CMD + A and then CTRL/CMD + C)

6. Go back to the tab where you have the script open. Paste the new content.

7. Save the script as shown in the picture below.

8. Close the tab and update the file page. The Fanfiction Management menu might take a few minutes to appear.

The script has been updated also to public Log files, so you can always make a copy of it for yourself and copy & paste all the old content from the old file. However, since I'm most likely releasing version 2.1 within the next few weeks, you might want to wait for it. With the new version release I recommend strongly making a new copy and I will not give out instructions to make edits other than the complete fix for this script. If everything goes as planned, there will be a few new features I've been either working on already since before the release of 2.0 or someone has requested it within these first two months. Find the links to the file from this link.

[huurrefanfictionreadinglog]

Fetch Data script has a problem

Just a heads up before I get multiple messages about this bug and you know that I am looking for it. At the moment, my Fetch Data from AO3 links script does not work well with Not Rated, Explicit and Mature fics, filling only the language, word count and chapters. I suspect that something has changed in the base code in AO3 so I am looking for it.

I hope I can get this problem fixed soon! In the meantime, the easiest way to fill in needed information about those fics is to download an HTML file. That way, when you copy and paste tags, there are commas between them. :)

I will update you as soon as I know the fix!

[huurrefanfictionreadinglog]

Update

The problem was figured out! However, I have to rebuild the first part of the script again and it will take a bit. I hope I get it done during the weekend but I estimate that it will need at least 10 hours of work and I'm not so sure I have that much during the weekend.

[huurrefanfictionreadinglog]

Update 02/17/2025

Still no fix, sorry :( I'm facing more problems than I thought possible, but I have some progress. I can work the script only 2-3 hours per day on weekdays before I get a headache and with my way of working, it is not a lot. I will try to get the fix ready this week, but in case that is not possible, I will publish some fixes for the script on Sunday (02/23/2025).

Remember, that you can always save only the link to the file in the meantime if you don't want to fill information manually!

(I will be adding a few other things at the same time since I had planned them already and they were easy to add. After this bug fix, if the fic is locked, the file knows to tell that instead of leaving just everything empty!)

[huurrefanfictionreadinglog]

Update 02/18/2025

I have some good news! I'm close to resolving this problem. At the moment, I can get the script to pick up everything else but the fandom. This is a big thing for me because earlier today the script was completely broken at one point. (I'm pretty sure any IT/coding professional would be watching me working this with horror...). I forgot I had a few deadlines this week for school so I might not get this ready tomorrow, but I believe strongly that it'll be fine before the weekend.

And I want to thank everyone for their kind words <3 I know I'm doing this completely free and I have my day job and studies and writing and everything, but my background is in retail and customer service and my heart doesn't allow me to force people to wait longer than they need to. I'm always really thankful for everyone who points out a bug, error or anything else that's weird and I always do my best to get everything sorted as quickly as possible.

With this bug fix, I'll also publish a version of the script where you have only either AO3 script with or without fandom in tags. I use always the one without fandom mentioned in tags (because I read basically only one fandom) and some people use only the one with fandoms in tags.

I have also a kind of bad news: Because the script has to go through two versions of patterns with Mature/Explicit/Not Rated fics, it will take a bit longer.

Now I'm off to write for an hour before I have to get to bed. :D I said an hour ago I would do that but I still continued with this script. I have also a Discord server for this file where I've been updating my progress, so you are always welcome to join us there if you're interested. It's not the busiest server and I avoid tagging everyone unless there is something really big. I have a cute bot welcoming you because I'm truly terrible with that kind of thing (I'm sorry for everyone who would've waited for my greeting) and you are always welcome to give suggestions, wish for features, report bugs, ask for help, ask for how to do something and overall discuss the file (and also other things). Join Discord here: https://discord.com/invite/2CTuh3rQXG

(With the new bug fix, I will officially publish version 2.1 since I've made quite a few edits since version 2.0 was released. 👀 I'm checking out if I can add one requested feature which should be fairly easy and finally see if the combined tag settings in the AO3 script work well enough for release.)

[huurrefanfictionreadinglog]

Fetch Data script has a problem

Just a heads up before I get multiple messages about this bug and you know that I am looking for it. At the moment, my Fetch Data from AO3 links script does not work well with Not Rated, Explicit and Mature fics, filling only the language, word count and chapters. I suspect that something has changed in the base code in AO3 so I am looking for it.

I hope I can get this problem fixed soon! In the meantime, the easiest way to fill in needed information about those fics is to download an HTML file. That way, when you copy and paste tags, there are commas between them. :)

I will update you as soon as I know the fix!

[huurrefanfictionreadinglog]

Update

The problem was figured out! However, I have to rebuild the first part of the script again and it will take a bit. I hope I get it done during the weekend but I estimate that it will need at least 10 hours of work and I'm not so sure I have that much during the weekend.

[huurrefanfictionreadinglog]

Update 02/17/2025

Still no fix, sorry :( I'm facing more problems than I thought possible, but I have some progress. I can work the script only 2-3 hours per day on weekdays before I get a headache and with my way of working, it is not a lot. I will try to get the fix ready this week, but in case that is not possible, I will publish some fixes for the script on Sunday (02/23/2025).

Remember, that you can always save only the link to the file in the meantime if you don't want to fill information manually!

(I will be adding a few other things at the same time since I had planned them already and they were easy to add. After this bug fix, if the fic is locked, the file knows to tell that instead of leaving just everything empty!)

[huurrefanfictionreadinglog]

Fetch Data script has a problem

Just a heads up before I get multiple messages about this bug and you know that I am looking for it. At the moment, my Fetch Data from AO3 links script does not work well with Not Rated, Explicit and Mature fics, filling only the language, word count and chapters. I suspect that something has changed in the base code in AO3 so I am looking for it.

I hope I can get this problem fixed soon! In the meantime, the easiest way to fill in needed information about those fics is to download an HTML file. That way, when you copy and paste tags, there are commas between them. :)

I will update you as soon as I know the fix!

[huurrefanfictionreadinglog]

Update

The problem was figured out! However, I have to rebuild the first part of the script again and it will take a bit. I hope I get it done during the weekend but I estimate that it will need at least 10 hours of work and I'm not so sure I have that much during the weekend.

[huurrefanfictionreadinglog]

Fetch Data script has a problem

Just a heads up before I get multiple messages about this bug and you know that I am looking for it. At the moment, my Fetch Data from AO3 links script does not work well with Not Rated, Explicit and Mature fics, filling only the language, word count and chapters. I suspect that something has changed in the base code in AO3 so I am looking for it.

I hope I can get this problem fixed soon! In the meantime, the easiest way to fill in needed information about those fics is to download an HTML file. That way, when you copy and paste tags, there are commas between them. :)

I will update you as soon as I know the fix!

[huurrefanfictionreadinglog]

Reading Status Statistics giving "!REF" when using all four statuses

You have no idea how much I love that I've arranged a chance to report bugs so easily through the form that's linked in the Home tab in the file. I should probably figure out something that the form would note me if there is a new submission, but I usually check it almost daily and I hope (fingers crossed now that I say this) that there will be no acute bugs at any point. But yes, with these words to the bug that I checked now (and as always, I've edited this to the original files):

One of the users informed me that when you use all four reading statuses (TBR/Reading/Read/Did not finish), the Status Statistics box in the Home tab gives a reference error. I have no logical reason why UNIQUE formula would pick up five values when there are only four of them but it does.

The reason is my warning cell which is right under it so the fix is quite easy. I added the warning later, on January 3rd probably, so if you've made your copy before that, you don't have any problems. That's also the reason why this got through my fingers. :D

SO. There are technically two options: you can either delete the warning (it was mostly to notify everyone about that so no one would need to start their file again for deleted columns) completely/move the text to the Instructions tab OR if you want it to be as a reminder, unmerge the cell, move the text from cell J12 to J13 and merge J13:L15 again.

Thankfully quite an easy fix this time! :) I had anticipated it would need more time when I saw last night that there was a new bug report, so I'm gonna work on especially the bug in Most popular in this fandom section for some time. It's still unfortunately a mystery to me, but I'm working on it! I'm also trying to figure out a few bigger improvements that I could hopefully get out as version 2.1 before summer. With all the new versions, I will offer instructions on how to add those improvements to the file you have already so you wouldn't need to change it unless you really want to. :)

[huurrefanfictionreadinglog]

Bug fix for Yearly Statistics

You can find the same blog post from Huurreauthor.com.

The first week after the release was definitely the busiest with bug reports and fixing them. There is one bug that has been such a nuisance and I'm still trying to get it fixed. It appears in the General Statistics tab with the Most popular in this fandom with some fandoms. I'm trying to map out if there is a specific pattern for this, so please, if you notice this bug, report it through the Bug Report form with the information of with fandom it appears.

I've got also some reports from the Fetch Data script when it doesn't do what it should and gives an error message TypeError: Cannot read properties of undefined (reading 'forEach'). So far it seems that it's maybe something on AO3's end (for example slowness as they have also reported that AO3 has been slow lately). So far the script has worked to the same link some time later.

If the script doesn't get the data to the file and does not show any error messages, the fanfic is most likely locked and therefore the script doesn't work on it.

I've got multiple good questions about the uses of different things and "Can I do this or that" in both Discord and Tumblr. I will gather them together soon, probably doing some kind of a collection blog post. Tumblr is a really good place to ask anything anonymously, but it is also possible through the Request a feature or leave feedback form that is linked to the file's Home tab. You don't need to leave your contact information and if there is a question without an email address, I will answer it at least in Tumblr. :) 

But now! To the real bug fix! I did this a bit differently because there were so many formulas to fix. For some reason, Most Popular Fandom and Most Popular Pairing have been giving random results in Yearly Statistics. These are already fixed to the public files so you can always make a new copy for yourself and copy fic information from your old file to the new one. I simplified the formulas a lot, although it meant also leaving out something. In this case, it doesn't count re-read fics when looking for the most common value. However, it will count them when the most common value is found.

First of all, you can find all the formulas and probably good enough instructions from this Google Sheets File. You can copy & paste fixed formulas for every year to the hidden support area you can find when you open the Yearly Statistics tab and click a small arrow in the top right corner. 

You can find the specific cell you should choose (but only click it once to choose it, not twice to activate it!) from the file. Note that the location is slightly different depending on if you have starting from 2024 or starting from 2025 version.

For additional help, please see the video below and if you need help further, please send an email or join my Discord! We can do it over screen share too, if necessary. (Though, it's not my favourite option and I can imagine that it's not that for other people either, especially with completely random, so I always try to get the problem sorted without that.)

[huurrefanfictionreadinglog]

Love the tracker, it works perfectly for me! I've been reading so much more since the year started and being able to neatly keep track of everything is definitely part of why, so thank you very much for making and sharing it! I'm curious why some categories on the general stat page have extra rows, like the rating and warning? is it in case ao3 adds more in the future or if a user wants to add a custom rating/warning to their version of the tracker? Thank you! Hope your'e having a lovely day!

Hi and thank you for the comment and I'm really glad it has also encouraged you to read more! <3 It was one of the reasons I wanted to do this.

I think AO3 is the most used fanfiction website, at least within the users of this log. However, there are also other websites so I wanted to have extra rows to make sure that users can log whatever they want. If you use only AO3, you can create a few of your own and use them when you want to.

As my mother tongue is not English and even though I mostly read fanfiction in English, I read it also in my mother tongue from local fanfiction forum. It doesn't use warnings the same way as AO3 uses and even though I try to combine them, I might need to create a new one that describes better that warning.

Same with the ratings! Different countries might have different ratings and more levels in them than AO3.

Concluding this together: I wanted to offer something to also other than AO3 users. :)

[huurrefanfictionreadinglog]

Hi, sorry if you answered that already but I just found your amazing work when looking for a way to track my fanfics this year but I am not able to make a copy of it because I always get a notification that currently the file cannot be open.. do you know what the issue could be there and how to fix it ?

Hi! Hmm, I just tested both versions, starting in 2024 and starting in 2025 and I could make a copy of them without any problems, so I guess that this is more on Google's end than anywhere else. Have you checked Google's help (for example in this article are some troubleshooting instructions if you cannot open a file).

If you still cannot make a copy of the file, email me at [email protected] so we can better walk through different possibilities. I can for example create an editable version for you that I can move under your ownership. I guess that this should at least work! :)

[huurrefanfictionreadinglog]

Wow! This sheet is so much more advanced than any attempts at tracking I've made in the past. I LOVE it! I'm wondering how you suggest marking unfinished, still regularly updating works in the TBR/Reading/Done/DNF column? Do you usually mark them as Read if you're caught up on the latest update or leave them as Reading until it's finished(or abandoned)? I can't decide what I prefer, and I keep going back and forth on which to use. Would love to hear what your intention was!

Thank you for the nice words!! <3

So, this is actually one of the things that I just left for users to decide how they want to do it. I tried to figure out how to do this part logically, but in the end, it was impossible. But how do I do that?

If the fic is getting regular updates/the latest update was not that long ago (like, within a year or something), I keep it in "reading".

If the last update was more than a year ago, I mark it "read".

I've figured this way is the best for me because when I'm reading something that gets regular updates, I don't have to reread more than max last paragraph of the previous chapter. If it's longer from the updates, the chances that I'm going to reread the whole fic again when it gets an update are high. Because then, after rereading, I can mark the date to reread area.

I'd like to have better routine so I could go f.e. once a month through all the fics I've marked "reading", but nope, I forget it all the time. But that's what I would do if I was better at using the tool I made first for myself 😂

Not probably the answer you hoped for, but maybe this could give some ideas!

[huurrefanfictionreadinglog]

Hi! I'm loving the log! However, the Average Review column on the Author Stats page doesn't populate when I update the page like everything else. It's not an important part of the sheet for me, so if it just won't work, I don't mind! I'll just hide it if that's the case, but I figured I'd ask if you have any ideas why that might be? It could be user error, but I only started using the log today and don't think I've done anything to break the sheet. Thanks for all the work that went into the log!

Hi and thank you for the feedback and also for the report about this problem! Average Review comes actually with a formula and I forgot completely that it was that way. Just before releasing this version, I made quick tests of my own with the original file (stupid me) and when deleting my test fics, I just deleted everything without realising that there were formulas. Whoops. However, it's a really easy fix!

The formulas start again from row 28. Choose cell J28 and you can see a small blue circle:

Grab it and pull it upwards all the way up to row 3 and it copies the formula to those cells.

I hope you enjoy the use of this in the future too! 😊 There are most likely still some small bugs, but it seems that the biggest ones are fixed so far.

[huurrefanfictionreadinglog]

Did you report a bug about "did not finish" status breaking Status Statistics? Could you DM me?

My bad that I didn't include any place to put down your email when reporting bugs through bug report form, but in case you see this post, could you send a message?

Or, if anyone else encounters the same bug when you set the reading status to "did not finish", it makes the status statistics break in the Home tab (see the picture below), could you send me a message? :) Since I couldn't recreate this, I'm working blindly.

However, if you encounter this kind of error (usually means that it can't find something that the formula is pointing at), check that you have the formulas in those cells exactly the same as in this picture below! If you haven't deleted any rows or columns, this should be right. (Status Statistic header starting in Home tab from cell J6.)

And adding a place for email to the bug report form will be on my to-do list first thing tomorrow!

I keep a "bug master list" in the Discord channel. I try to create a similar one soon here and website too, but I had to take an easier time without thinking about this as much. The number of bugs thankfully decreased, but I have still one to work through (Most popular in this fandom... might not give results to every fandom you have).

Thank you for all the feedback, support and everything! I'm overwhelmed with it and I haven't even shared this to Reddit yet since I wanted to fix the most acute bugs first without as many users. Maybe I could gather enough courage to do it tomorrow...

[huurrefanfictionreadinglog]

Fix for All Time Statistics

You can find this post also from my website: https://www.huurreauthor.com/news/fix-for-all-time-statistics

Someone informed me that when copying the formulas and codes from Tumblr posts, the quotation marks turn wrong. You're still free to check out the steps in this post.

Bug after bug after bug. I am really thankful for the Discord Server where people have reported these problems whenever they notice anything amiss or wrong. Without them, it would be a lot more difficult to find them. You can join our Discord server through this link. I'm keeping also a master list of all known bugs there for everyone to see. While I'm quick to fix them at the moment, I don't see it necessary to keep that kind of list in the blog. However, I've now collected all the bug-fix posts to the Help page of my website too! 

One of the users noticed that they had wrong values in All Time Statistics in the Yearly Statistics tab. Some fighting and figuring out later, I'm here to give you fixes. First of all, I left the hidden support columns in the Yearly Statistics tab in such a messy state that I'm embarrassed that you have to see them, but... well, nothing I can do now. So, let's get to work, you know the jazz, I'll give you every step and cell and formula and you'll just follow them and hopefully it will work out! As always, these are already fixed to public files so you can always go to make a new copy for yourself and check out from there how they are set.

1. Grab the Yearly Statistics tab and open hidden columns.

2. Scroll to the right until you see columns Y, Z, AA, AB, AC and AD.

3. In the 2024 version, choose cell Z19. In the 2025 version, choose cell Z3. Hox! On the left side of them, is the text Fandom. Replace the old formula with this one:

=IFERROR(INDEX(UNIQUE(FILTER(R_Fandom, F_ReadingStatus="Read")), MATCH(MAX(COUNTIF(FILTER(R_Fandom, F_ReadingStatus="Read"), UNIQUE(FILTER(R_Fandom, F_ReadingStatus="Read")))), COUNTIF(FILTER(R_Fandom, F_ReadingStatus="Read"), UNIQUE(FILTER(R_Fandom, F_ReadingStatus="Read"))), 0)),"")

4. Go to one row down, so in the 2024 version cell Z20 and in the 2025 version cell Z4. Replace the old formula with this one:

=IFERROR(INDEX(UNIQUE(FILTER(S_MainPairing, F_ReadingStatus="Read")), MATCH(MAX(COUNTIF(FILTER(S_MainPairing, F_ReadingStatus="Read"), UNIQUE(FILTER(S_MainPairing, F_ReadingStatus="Read")))), COUNTIF(FILTER(S_MainPairing, F_ReadingStatus="Read"), UNIQUE(FILTER(S_MainPairing, F_ReadingStatus="Read"))), 0)),"")

5. Go to one row down, so in the 2024 version cell Z21 and in the 2025 version cell Z5. Replace the old formula with this one:

=IFERROR(INDEX(UNIQUE(FILTER(O_Rating, F_ReadingStatus="Read")), MATCH(MAX(COUNTIF(FILTER(O_Rating, F_ReadingStatus="Read"), UNIQUE(FILTER(O_Rating, F_ReadingStatus="Read")))), COUNTIF(FILTER(O_Rating, F_ReadingStatus="Read"), UNIQUE(FILTER(O_Rating, F_ReadingStatus="Read"))), 0)),"")

I know, I might often overdo formulas, stacking them on top of each other more than would be needed, but it's better to be safe than sorry.

I would like to remind you now that when counting the most appearing values, it only takes first-time reads into account. While counting how many of them are read will also count rereads. With Most read fandom, pairing and rating in All time statistics, it counts only first-time reads so basically the reading statuses. I will probably edit formulas one day to count in rereads too but it's something for a later date.

I'm also sorry for all the times I wrote raiting instead of rating! English is not my first language and I'm often having problems with that specific word.

I will probably be back at least once during the weekend, but hopefully, I can also focus on relaxing!