It's unlikely that a large volume of text will be generated at the base rate (errors compound), so the number might be higher than we expect.
(Here is a reference to K&R, the standard first reference to C, because I am obligated to make such a reference.)
https://progforperf.github.io/Expert_C_Programming.pdf
If you’re a C programmer, old or new, and haven’t encountered this book: Stop What You Are Doing And Go Read It! It’s amazing.
For me a breakthrough moment was when I saw my C code interleaved with the generated assembly. Registers, calling conventions, calling OS functions…all laid bare!
And when I bring up that this should be clearly marked, preferably up front, it's often taken as a personal slight.
I realize this is a me problem to some extend, I shouldn't feel strongly about this, but I do.
You can guess, but there is no single objective test that is 100% accurate.