This works in the latest versions, most likely all versions after 13.3, since the game won't retrieve the textures for the icons in earlier versions as the game does in later versions. I may see what I can do to make this work on those too.
The clock face is also currently in an alternate version where the two last digits are made smaller to fit all five digits.

---

Updated at 15:05 on 04.05.2024, containing 364 numbers.

I think one should be able to know what time of day it is. Just as one can see the coordinates, block stage or biome in F3, I also think that one should not be prevented from seeing the current Daytime/Gametick. But since it isn't in F3, I made this simple texture pack that roughly shows on the clock what the daytime/gameticks is when the clock changes state. Because one is not always available or allowed to use the command: "/ time query daytime" or "/ time add 0".

If thou want a specific amount of gameticks to be shown, just let me know. Do not hesitate. It is very easy to make a special amount of gametick appear, but it is very time-consuming to do that work for all the 240 gameticks of the 24 000 gamticks. I may later work on a way to show all digits of the Daytime.

One important thing to know is how the numbers appear on the clock. The fact is that the clock is only 14 pixels wide. And I couldn't find a better way to write the numbers, so each of the digits needs 4 pixels. This means that there is only room for 3 digits without overriding the vanilla design. The maximum gametick is 24 000. To show all the numbers, I have included only the first three digits at all stages. Here are some examples:

number on clock	actual daytime/gametick	codetime I use for time the clock correctly
008 35	835	0,8198233
024 45	2 445	0,8834901
126 36	12 636	0,2433127
230 51	23 051	0,7426013
240 00	24 000	0,7844747

I don't know how to fit all digits aesthetic good to make the clock count evenly yet. So in this pack the clock skips between the numbers since I have only added double the amount of the vanilla 64 amounts of clock stages. 107 more in fact. That means it will jump from 194, to 197, and thereafter to 200 etc. But I do know how to find all the codetime to show all 24 000 digits, by using some automatic means. But that means all five digits will not be shown, and it will jump between all the 24 000 stages according to the codetime.

If I just could find a tool that could generate the codetime numbers needed to link the json-files for the gameticks to be chosen at the right time. Right now, I am stuck with manually test which exact digits I need to use for the codetime to get the timing right. I have tried to calculate the codetime for the gametime in Excel, but it has not generated correct numbers yet.

The json file I used was originally were from 1.14.4, and I have used the pack in all versions since then, but I do not know if it will work in earlier versions. But it works later versions to. I think I can make it so it works in earlier versions than 1.13.2 if someone wants it. Probably not even difficult.
Just ask if so.

Just let me know if there are problems, faults, errors. The clock.json-file is relying on correct writing in the code to be able to do many combinations of a few textures into one item, so there could easily be some faults in the working.