Skip to content
Botlero

Corrections

Every value Botlero has stopped publishing is kept, not deleted, with the reason that was recorded when it was withdrawn and a link to the page that published it. Newest first, across every robot.

An entry says a value stopped being published and why. It does not say what replaced it: often nothing did, and where something did, the replacement is on the robot's own page with its source and its date.

Two kinds of recorded change are not withdrawals, and are not listed here. A robot going live is a publication rather than a value being taken away, so those are listed by month below, under “robots added”. And where a value was withdrawn but the old value itself was never recorded, the reason is kept but there is nothing to show, so no entry is made for it.

RSS feed of new robots and corrections

683 withdrawn values · 485 recorded reasons · newest 2026-09-30

2026-09-29279 values, 279 reasons · 40 on this page

  1. the quote states battery CHARGING time ("充电时长 2.0 h", "Charging Time", "Charging: 2 hours"), which is a different concept from the time to swap a battery — review-flagged on the galbot-s1 dry run, then judged by hand against its own registry row. Quote: "Charging Time Single-battery adapter charging 2.0 h"

    1. Galbot S1Battery swap time2026-09-29 · specification

      7200

    1 value · recorded by cleanup-new5c-2026-09-29 · statement 6abbbbd392258c2e14c9a514 · link to this reason

  2. the quote states battery CHARGING time ("充电时长 2.0 h", "Charging Time", "Charging: 2 hours"), which is a different concept from the time to swap a battery — review-flagged on the galbot-s1 dry run, then judged by hand against its own registry row. Quote: "充电时长 2.0 h"

    1. Galbot S1Battery swap time2026-09-29 · specification

      7200

    1 value · recorded by cleanup-new5c-2026-09-29 · statement 6abbbbd36b267f729bb903a0 · link to this reason

  3. a CONTINUOUS or plain payload ("continuous 50 kg dual-arm payload", "General Payload", "Nutzlast", "Payload 50.0 kg") where this key is the PEAK — verbatim what that row's NOT text excludes, and the same class closed in cleanup-new5b — review-flagged on the galbot-s1 dry run, then judged by hand against its own registry row. Quote: "continuous 50 kg dual‑arm payload"

    1. Galbot S1Peak payload2026-09-29 · specification

      50

    1 value · recorded by cleanup-new5c-2026-09-29 · statement 6abbbbd344505e56ee976b12 · link to this reason

  4. a CONTINUOUS or plain payload ("continuous 50 kg dual-arm payload", "General Payload", "Nutzlast", "Payload 50.0 kg") where this key is the PEAK — verbatim what that row's NOT text excludes, and the same class closed in cleanup-new5b — review-flagged on the galbot-s1 dry run, then judged by hand against its own registry row. Quote: "Payload 50.0 kg"

    1. Galbot S1Peak payload2026-09-29 · specification

      50

    1 value · recorded by cleanup-new5c-2026-09-29 · statement 6abbbbd352402acfed67d73f · link to this reason

  5. a CONTINUOUS or plain payload ("continuous 50 kg dual-arm payload", "General Payload", "Nutzlast", "Payload 50.0 kg") where this key is the PEAK — verbatim what that row's NOT text excludes, and the same class closed in cleanup-new5b — review-flagged on the galbot-s1 dry run, then judged by hand against its own registry row. Quote: "unprecedented 50 kg continuous dual-arm payload"

    1. Galbot S1Peak payload2026-09-29 · specification

      50

    1 value · recorded by cleanup-new5c-2026-09-29 · statement 6abbbbd34e18dd2bec322297 · link to this reason

  6. "ROS-compatible" / "ROS2-compatible" states what the stack is compatible WITH, not what middleware the robot runs — the class closed on agibot-x1 in cleanup-open40 — review-flagged on the galbot-s1 dry run, then judged by hand against its own registry row. Quote: "OS: Proprietary (ROS2-compatible)"

    1. Galbot S1Middleware2026-09-29 · specification

      ROS2

    1 value · recorded by cleanup-new5c-2026-09-29 · statement 6abbbbd3fd8bae54035260d1 · link to this reason

  7. either the cameras are OPTIONAL ("选配腕部相机×2") or the quote describes ONE stereo unit (a single ZED 2i, "dual RGB cameras ×1") while the filed value is 2 — no page states the number filed — review-flagged on the galbot-s1 dry run, then judged by hand against its own registry row. Quote: "Camera Head: dual RGB cameras ×1"

    1. Galbot S1Camera count2026-09-29 · specification

      1

    1 value · recorded by cleanup-new5c-2026-09-29 · statement 6abbbbd3c6c32d158517c7ea · link to this reason

  8. either the quote says MAXIMUM load ("最高负载 50 KG", "最高 50KG 负载"), which belongs to limitingLoadKg, or it is a per-arm or ambiguous "General Payload" figure that this row's NOT text sends to loadPerArmKg — review-flagged on the galbot-s1 dry run, then judged by hand against its own registry row. Quote: "Payload 5 kg"

    1. Galbot S1Rated payload2026-09-29 · specification

      5

    1 value · recorded by cleanup-new5c-2026-09-29 · statement 6abbbbd38c13842f894d921c · link to this reason

  9. either the quote says MAXIMUM load ("最高负载 50 KG", "最高 50KG 负载"), which belongs to limitingLoadKg, or it is a per-arm or ambiguous "General Payload" figure that this row's NOT text sends to loadPerArmKg — review-flagged on the galbot-s1 dry run, then judged by hand against its own registry row. Quote: "最高 50KG 负载"

    1. Galbot S1Rated payload2026-09-29 · specification

      50

    1 value · recorded by cleanup-new5c-2026-09-29 · statement 6abbbbd38231f67c669d2419 · link to this reason

  10. either the quote says MAXIMUM load ("最高负载 50 KG", "最高 50KG 负载"), which belongs to limitingLoadKg, or it is a per-arm or ambiguous "General Payload" figure that this row's NOT text sends to loadPerArmKg — review-flagged on the galbot-s1 dry run, then judged by hand against its own registry row. Quote: "最高负载 50 KG"

    1. Galbot S1Rated payload2026-09-29 · specification

      50

    1 value · recorded by cleanup-new5c-2026-09-29 · statement 6abbbbd3d5c575cf97ad187b · link to this reason

  11. the quote reads "Horizontal 0–2400 mm; vertical 2390 mm" and the value filed is 0 — a range start read as the whole fact — review-flagged on the galbot-s1 dry run, then judged by hand against its own registry row. Quote: "Reach Horizontal 0–2400 mm; vertical 2390 mm (wrist center)"

    1. Galbot S1Workspace height range2026-09-29 · specification

      0

    1 value · recorded by cleanup-new5c-2026-09-29 · statement 6abbbbd39e1d539a320fd487 · link to this reason

  12. the quote states a REACH ("Arm reach: 920 mm", "Reach 65 cm"), which that row's NOT text names explicitly — review-flagged on the galbot-s1 dry run, then judged by hand against its own registry row. Quote: "Arm reach: 920 mm"

    1. Galbot S1Arm length2026-09-29 · specification

      920

    1 value · recorded by cleanup-new5c-2026-09-29 · statement 6abbbbd3569de93b75cc5b46 · link to this reason

  13. "Arm reach: 920 mm" is the arm, and the same page publishes the robot's reach as 2.4 m — review-flagged on the galbot-s1 dry run, then judged by hand against its own registry row. Quote: "Arm reach: 920 mm"

    1. Galbot S1Reach2026-09-29 · specification

      0.92

    1 value · recorded by cleanup-new5c-2026-09-29 · statement 6abbbbd36545288009953895 · link to this reason

  14. the value contradicts the robot's own published mass by an order of magnitude (10 kg against 100-110 kg; 55 kg against 320 kg), so it belongs to a component or another machine — review-flagged on the galbot-s1 dry run, then judged by hand against its own registry row. Quote: "Weight 55 kg"

    1 value · recorded by cleanup-new5c-2026-09-29 · statement 6abbbbd3014c7692270fa278 · link to this reason

  15. the quote either calls the sensor OPTIONAL ("腕部可选配六维力传感器", "Optional six-axis wrist force sensor") or places it at JOINT level ("force/torque (joint-level)"), so neither states a sensor built into the hand — review-flagged on the rainbow-rb-y1 dry run, then judged by hand against its own registry row. Quote: "Sensors IMU, force/torque (joint-level), proprioceptive position/torque"

    1. RB-Y1Hand sensors2026-09-29 · specification

      FORCE_TORQUE

    1 value · recorded by cleanup-new5c-2026-09-29 · statement 6abbbf1a11bd11204233c6de · link to this reason

  16. a maximum allowable moment on a CROSS BEARING is a structural limit of a component, not a joint's peak output torque — review-flagged on the rainbow-rb-y1 dry run, then judged by hand against its own registry row. Quote: "Maximum Allowable Moment (Based on Cross Bearing) 46.4 Nm"

    1. RB-Y1Joint torque (per joint)2026-09-29 · specification

      46.4

    1 value · recorded by cleanup-new5c-2026-09-29 · statement 6abbbf1a5ccb0fd496212111 · link to this reason

  17. "Nominal torque" is the continuous rating, and this key is the PEAK — the maker's own "Max. intermittent torque 30 Nm" on the same table is the peak and is kept — review-flagged on the rainbow-rb-y1 dry run, then judged by hand against its own registry row. Quote: "Nominal torque 5.4 Nm"

    1. RB-Y1Joint torque (per joint)2026-09-29 · specification

      5.4

    1 value · recorded by cleanup-new5c-2026-09-29 · statement 6abbbf1a741f0fb95862340d · link to this reason

  18. a maximum allowable moment on a CROSS BEARING is a structural limit of a component, not a joint's peak output torque — review-flagged on the rainbow-rb-y1 dry run, then judged by hand against its own registry row. Quote: "Maximum Allowable Moment (Based on Cross Bearing) 46.4 Nm"

    1. RB-Y1Joint torque (per joint)2026-09-29 · specification

      46.4

    1 value · recorded by cleanup-new5c-2026-09-29 · statement 6abbbf1a2b8765484a2892ff · link to this reason

  19. "Nominal torque" is the continuous rating, and this key is the PEAK — the maker's own "Max. intermittent torque 30 Nm" on the same table is the peak and is kept — review-flagged on the rainbow-rb-y1 dry run, then judged by hand against its own registry row. Quote: "Nominal torque 5.4 Nm"

    1. RB-Y1Joint torque (per joint)2026-09-29 · specification

      5.4

    1 value · recorded by cleanup-new5c-2026-09-29 · statement 6abbbf1acc417fbb3260da72 · link to this reason

  20. a bare country or nationality cell ("Nationality China", "Country China", "China") with no statement about where the robot is MADE — the class closed in both earlier cleanups — review-flagged on the rainbow-rb-y1 dry run, then judged by hand against its own registry row. Quote: "South Korean company"

    1. RB-Y1Made in2026-09-29 · specification

      KR

    1 value · recorded by cleanup-new5c-2026-09-29 · statement 6abbbf1aa1d248e9926c2aa8 · link to this reason

  21. a plain "Payload" cell states no per-arm figure, which this key requires — review-flagged on the rainbow-rb-y1 dry run, then judged by hand against its own registry row. Quote: "Payload | 3 kg"

    1. RB-Y1Payload per arm2026-09-29 · specification

      3

    1 value · recorded by cleanup-new5c-2026-09-29 · statement 6abbbf1aa145c72b14718c9c · link to this reason

  22. the quote calls the sensor OPTIONAL (an optional wrist force sensor, "Optional RGB-D cameras on both wrists"), so it is not fitted to the robot as sold — review-flagged on the rainbow-rb-y1 dry run, then judged by hand against its own registry row. Quote: "LiDAR for autonomous navigation (optional)"

    1. RB-Y1Sensors2026-09-29 · specification

      LIDAR

    1 value · recorded by cleanup-new5c-2026-09-29 · statement 6abbbf1aa01c4aaa1d1a0ade · link to this reason

  23. a tilde is a hedge, which that row's NOT text excludes — review-flagged on the rainbow-rb-y1 dry run, then judged by hand against its own registry row. Quote: "Commercial~$80,000"

    1. RB-Y1Price from (USD)2026-09-29 · specification

      80000

    1 value · recorded by cleanup-new5c-2026-09-29 · statement 6abbbf1acef31f2a35c28e36 · link to this reason

  24. the quote lists APPLICATIONS and states no user type — review-flagged on the rainbow-rb-y1 dry run, then judged by hand against its own registry row. Quote: "AI-driven mobile manipulation tasks in manufacturing, logistics, and research."

    1. RB-Y1User type2026-09-29 · specification

      PROFESSIONAL

    1 value · recorded by cleanup-new5c-2026-09-29 · statement 6abbbf1af3947a66656a4668 · link to this reason

  25. derived from a directory's own empty "Indicative price Undisclosed" field while other sources publish a price — review-flagged on the rainbow-rb-y1 dry run, then judged by hand against its own registry row. Quote: "Indicative price | 80000.0 USD"

    1. RB-Y1Price status2026-09-29 · specification

      LIST

    1 value · recorded by cleanup-new5c-2026-09-29 · statement 6abbbf1ab591d72a54aa4709 · link to this reason

  26. "Indicative price" is a hedge, which that row's NOT text excludes — the class closed in cleanup-new5b — review-flagged on the rainbow-rb-y1 dry run, then judged by hand against its own registry row. Quote: "Indicative price | 80000.0 USD"

    1. RB-Y1Price from (USD)2026-09-29 · specification

      80000

    1 value · recorded by cleanup-new5c-2026-09-29 · statement 6abbbf1a186610c3544d8b79 · link to this reason

  27. either the quote says MAXIMUM load ("最高负载 50 KG", "最高 50KG 负载"), which belongs to limitingLoadKg, or it is a per-arm or ambiguous "General Payload" figure that this row's NOT text sends to loadPerArmKg — review-flagged on the rainbow-rb-y1 dry run, then judged by hand against its own registry row. Quote: "3 kg | General Payload"

    1. RB-Y1Rated payload2026-09-29 · specification

      3

    1 value · recorded by cleanup-new5c-2026-09-29 · statement 6abbbf1ad53b6497eeadb98e · link to this reason

  28. a bare "Length" cell cannot prove body depth, and the maker's own size triple does not say which of its two footprint numbers is the depth — review-flagged on the rainbow-rb-y1 dry run, then judged by hand against its own registry row. Quote: "Length - 690 mm"

    1. RB-Y1Depth2026-09-29 · specification

      69

    1 value · recorded by cleanup-new5c-2026-09-29 · statement 6abbbf1a1aeaa3af21c69e76 · link to this reason

  29. the quote lists APPLICATIONS and states no user type — review-flagged on the rainbow-rb-y1 dry run, then judged by hand against its own registry row. Quote: "Primary applications include Industrial automation, manufacturing, logistics."

    1. RB-Y1User type2026-09-29 · specification

      PROFESSIONAL

    1 value · recorded by cleanup-new5c-2026-09-29 · statement 6abbbf1a91336705995af589 · link to this reason

  30. either the quote says MAXIMUM load ("最高负载 50 KG", "最高 50KG 负载"), which belongs to limitingLoadKg, or it is a per-arm or ambiguous "General Payload" figure that this row's NOT text sends to loadPerArmKg — review-flagged on the rainbow-rb-y1 dry run, then judged by hand against its own registry row. Quote: "Strength [kg] | 3"

    1. RB-Y1Rated payload2026-09-29 · specification

      3

    1 value · recorded by cleanup-new5c-2026-09-29 · statement 6abbbf1a1cb0a326e4c182ac · link to this reason

  31. the quote states a REACH ("Arm reach: 920 mm", "Reach 65 cm"), which that row's NOT text names explicitly — review-flagged on the rainbow-rb-y1 dry run, then judged by hand against its own registry row. Quote: "팔 도달범위: 600 (to wrist) + hand [mm]"

    1. RB-Y1Arm length2026-09-29 · specification

      600

    1 value · recorded by cleanup-new5c-2026-09-29 · statement 6abbbf1a4215a9e813d4e6c4 · link to this reason

  32. the quote states a REACH ("Arm reach: 920 mm", "Reach 65 cm"), which that row's NOT text names explicitly — review-flagged on the rainbow-rb-y1 dry run, then judged by hand against its own registry row. Quote: "Arm Reach: 600 (to wrist) + hand [mm]"

    1. RB-Y1Arm length2026-09-29 · specification

      600

    1 value · recorded by cleanup-new5c-2026-09-29 · statement 6abbbf1a2874f251b4b2bb2e · link to this reason

  33. "Cloud-assisted AI" says the AI uses the cloud; it does not state that the dependency is OPTIONAL, which is the value filed — review-flagged on the dexforce-w1-pro dry run, then judged by hand against its own registry row. Quote: "Cloud‑assisted AI"

    1 value · recorded by cleanup-new5c-2026-09-29 · statement 6abbbe02048765451ae1ca6b · link to this reason

  34. "Organizations exploring VLA-based humanoid control" describes a BUYER SEGMENT, not how this robot's AI is trained — review-flagged on the dexforce-w1-pro dry run, then judged by hand against its own registry row. Quote: "Organizations exploring VLA-based humanoid control and sim-to-real transfer."

    1 value · recorded by cleanup-new5c-2026-09-29 · statement 6abbbe02c24f3d2cfa3b3a02 · link to this reason

  35. "ROS-compatible" / "ROS2-compatible" states what the stack is compatible WITH, not what middleware the robot runs — the class closed on agibot-x1 in cleanup-open40 — review-flagged on the dexforce-w1-pro dry run, then judged by hand against its own registry row. Quote: "Operating system ROS-compatible + proprietary DexVerse/Sim2Real AI stack"

    1 value · recorded by cleanup-new5c-2026-09-29 · statement 6abbbe02ba43e35b603b40b3 · link to this reason

  36. either the cameras are OPTIONAL ("选配腕部相机×2") or the quote describes ONE stereo unit (a single ZED 2i, "dual RGB cameras ×1") while the filed value is 2 — no page states the number filed — review-flagged on the dexforce-w1-pro dry run, then judged by hand against its own registry row. Quote: "选配腕部相机×2"

    1 value · recorded by cleanup-new5c-2026-09-29 · statement 6abbbe02d890117234ddc33e · link to this reason

  37. the quote calls the sensor OPTIONAL (an optional wrist force sensor, "Optional RGB-D cameras on both wrists"), so it is not fitted to the robot as sold — review-flagged on the dexforce-w1-pro dry run, then judged by hand against its own registry row. Quote: "Force: Optional 6‑axis wrist force sensor"

    1 value · recorded by cleanup-new5c-2026-09-29 · statement 6abbbe0202cf44587df7ad20 · link to this reason

  38. the quote calls the sensor OPTIONAL (an optional wrist force sensor, "Optional RGB-D cameras on both wrists"), so it is not fitted to the robot as sold — review-flagged on the dexforce-w1-pro dry run, then judged by hand against its own registry row. Quote: "Depth Camera Optional RGB-D cameras on both wrists"

    1 value · recorded by cleanup-new5c-2026-09-29 · statement 6abbbe024236e4fdf33e6229 · link to this reason

  39. the quote calls the sensor OPTIONAL (an optional wrist force sensor, "Optional RGB-D cameras on both wrists"), so it is not fitted to the robot as sold — review-flagged on the dexforce-w1-pro dry run, then judged by hand against its own registry row. Quote: "力控感知：腕部可选配六维力传感器"

    1 value · recorded by cleanup-new5c-2026-09-29 · statement 6abbbe0206b7c8b3880bfa94 · link to this reason

  40. the quote either calls the sensor OPTIONAL ("腕部可选配六维力传感器", "Optional six-axis wrist force sensor") or places it at JOINT level ("force/torque (joint-level)"), so neither states a sensor built into the hand — review-flagged on the dexforce-w1-pro dry run, then judged by hand against its own registry row. Quote: "Force: Optional 6‑axis wrist force sensor"

    1 value · recorded by cleanup-new5c-2026-09-29 · statement 6abbbe020f5e4b1f3dc8bcbb · link to this reason

40 reasons per page. A robot's own withdrawals are listed on its page, under “Corrected values”. How a value gets published.