Dropping 419754 348560 507552 73836 459408 888354 448188 446904 851562 434760 736890 401814 248130 511554 739464 132210 853152 535068 49170 193896 86688 959328 408648 257488 818880 166768 246360 272232 944424 158502 16608 846648 647082 215808 417186 669300 541266 786210 566202 198048 61290 573480 360210 678496 903912 233320 431472 517140 75990 535892 918054 239700 252016 112500 156468 702688 140400 516486 20208 342228 306516 354522 526932 358674 62916 612576 48816 748244 399558 218580 303072 86160 409164 674664 490464 684756 287010 232960 350040 98904 927744 182484 614480 535200 125016 221640 609768 828798 913698 447072 556020 134832 39840 596664 175182 606600 853296 332874 964680 307944

Can i take 974610?
Pre-thanks

[QUOTE=vasyannyasha;458851]Can i take 974610?
Pre-thanks[/QUOTE]
It's not in the list. Probably because a smaller sequence merges with it (even smaller than [URL="http://factordb.com/sequences.php?se=1&aq=974610&action=range&fr=25&to=33"]114800[/URL]). I couldn't find in the forum here so it must be a really old merge.

My DB shows a merge to 102936 -> 114800 -> .... -> 974610 in the very early stage (i.e. known many years ago).

Edit: of course you can have 102936, is not taken.

[QUOTE=LaurV;458893]My DB shows a merge to 102936 -> 114800 -> .... -> 974610 in the very early stage (i.e. known many years ago).

Edit: of course you can have 102936, is not taken.[/QUOTE]

OK i take it. Thanks

[QUOTE=LaurV;458893]My DB shows a merge to 102936 -> 114800 -> .... -> 974610 in the very early stage (i.e. known many years ago).

Edit: of course you can have 102936, is not taken.[/QUOTE]

Well, now you (LaurV) have it. The script does not check if the keyword is before or after an eligible number. But this can easily be solved by dropping it again and vasyannyasha just needs to reserve it.

Grrrr.. Totally unintentional, and I don't have resources for it... No new sequences until I finish the old 22 that I have (read, get pissed off with them).

Dropping 102936.

Dropping 305460

Reserving 407232

Taking 370746.

Reservation tables were not updated for the last 2 months.

I tell you that Paul Zimmermann stopped calculations about 19560.
You can see the details on this page :
[URL="https://members.loria.fr/PZimmermann/records/aliquot.html"]https://members.loria.fr/PZimmermann/records/aliquot.html[/URL]
Aliquot sequence 19560 stopped at index 590 with c203 (tested up to 60 digits by ECM).

Up to now, at each iteration, each term of this aliquot sequence increases by a factor greater than or equal to 2 compared to the previous term.

Reserving 570288.