Deployment
GRIMME REXOR 6300 at Brandenburg
6-row self-propelled sugar beet harvester with cleaning and loading automation.
GRIMME REXOR 6300 by GRIMME · Catalog entry · 1 source · not yet field-verified
Machine-readable surfaces
- Markdown mirror: /deployments/grimme-rexor-6300-brandenburg-germany.md
- JSON-LD: embedded in this page’s head
- REST API: /v1/robots/bded17f6-a12c-4439-ad3f-f67c87d9b9b5
- Data documentation: /data
- Query this programmatically: Deploy MCP
European sugar beet and grain harvesting. GRIMME REXOR 6300 operations.
- Trust tier
- Catalog entry · 1 source · not yet field-verified
- Last updated
- 2026-06-08
- Model
- GRIMME REXOR 6300
- Company
- GRIMME
- Location
- Brandenburg
- Status
- operational
- ID
bded17f6-a12c-4439-ad3f-f67c87d9b9b5
Sources (1)
Methodology: Verified · 1 source (no primary) · last reviewed 2026-06-08
Verification posture
Verified
Low confidence
Review state
Stable
Last reviewed 2026-06-08
Maturity + lifecycle
Lifecycle: active
Architectural position
Cohort: harvester
Sources by quality tier
- 1
- unclassified
- Unclassified source
The framework is documented at /methodology. Corrections at /corrections. Reviewer: DEPLOY editorial team.
Methodology surface for GRIMME REXOR 6300 at Brandenburg.Common questions
- What is the GRIMME REXOR 6300 deployment at Brandenburg?
- GRIMME REXOR 6300, built by GRIMME, is recorded as a deployment at Brandenburg on the DEPLOY registry. GRIMME operates the deployment directly.
- Who operates GRIMME REXOR 6300 at Brandenburg?
- GRIMME, the manufacturer of GRIMME REXOR 6300, operates this deployment directly. This is a maker-deploys-its-own-product arrangement rather than a customer pilot.
- Have there been incidents at the GRIMME REXOR 6300 deployment at Brandenburg?
- No active incidents affecting this deployment are recorded on the DEPLOY registry. Absence of recorded incidents is not a guarantee no incident occurred; DEPLOY records only sourced incidents and suppresses retracted ones.
Deploy Watch
Track this deployment.
We notify you when status changes against primary-source evidence, contract events surface, or a related incident is filed.