Hi unconnected

You reported k=253 completed to n=3M. Do you also plan to double check 2-3M, and why? Do you have unreliable clients?
If so, please use only reliable ones.
How about k=29, do you plan (have to) double check it too?

And I noticed you reported your k=253 prime under a PrimeGrid prover's code. :confused::question:

[QUOTE=Kosmaj;323154]Hi unconnected

You reported k=253 completed to n=3M. Do you also plan to double check 2-3M, and why? Do you have unreliable clients?
[/QUOTE]
It was no *real* doublecheck. I looked through the my residue files and realizes that there were no data for range 1.75M-2M for k=253. Thus, I decided to make doublecheck.
[quote]
If so, please use only reliable ones.
How about k=29, do you plan (have to) double check it too?
[/quote]It is all ok with k=29. No reason to DC it.
[quote]And I noticed you reported your k=253 prime under a PrimeGrid prover's code. :confused::question:[/quote]I've created proof code L3345 but accidently reported my new prime under the Primegrid's L1224. Already wrote about this issue to the Dr. Caldwell.

All right, thanks for your replies and sorry for many questions.

Happy prime hunting and Happy New Year!

k=49 at n=2.80M

Status Report
 

k=7 at 3260k
k=21 at 2220k
k=35 at 2230k
k=77 at 1600k
k=97 at 1920k
k=181 at 1650k
k=199 at 1400k
k=239 at 1860k
k=225 at 1400k
k=297 at 1440k

Status report
 

k=107 now at n=1.4M, confirming the prime for n=1362654, no other primes.

k=9 tested to n=5M

k=73,85,91,163,209,299 tested to n=2M

The k<300 status page updated with latest results:

[url]http://www.15k.org/riesellist.html[/url]

k=139 from n=1310k
 

Taking k=139 from n=1310k.

status report
 

k=25 tested till n=2.96M
k=43 tested till n=3.23M
k=79 tested till n=2.34M
k=101 tested till n=3.39M
k=151 tested till n=3.2M