VTC fleets in Soria: a large province with no high-speed rail, Medinaceli station, the A-2 to Barajas and villages far apart; how the cars are shared between the capital, Almazán and the Moncayo and how the fleet gets paid

Where should the cars be in a province as large as Soria?

Spread out, because in Soria a car in the capital does not reach Ágreda or Arcos de Jalón in time. The capital, in the middle of the upper Duero, has Santa Bárbara hospital, the station with its few trains and the San Juan fiestas in late June; from it leave the early-morning Barajas runs along the A-15 and the A-2 and the Logroño trips over Piqueras. Almazán, to the south on the A-15, is the natural road to Medinaceli and Madrid. El Burgo de Osma and San Esteban de Gormaz, to the west, look to Aranda and the A-1. Ágreda and Ólvega, at the foot of the Moncayo, are the province's industrial hub, with shifts at hours with no bus, and are closer to Zaragoza than to Madrid. And Pinares, with Covaleda, Duruelo and San Leonardo, has the Laguna Negra in summer and snow on Santa Inés in winter. One car in the capital, another in Almazán or El Burgo and another in the Moncayo is the spread that covers the province.

The reference figures are the route engine's, the ones the customer sees before paying and on which the commission is calculated. The long run par excellence: Soria to Barajas, 220 km along the A-15 and the A-2, about 148 min and from 269,36 €; from the west, El Burgo de Osma to Barajas, 166 km via Aranda and the A-1. The medium connections with a train time: Almazán to Medinaceli station, 40 km from 59,77 €. The hospital, which brings the whole province in the morning: Ágreda to Santa Bárbara, 53 km, with a wait and a return. And the east: Soria to Zaragoza, 153 km along the N-122, for the high-speed train or the Aragonese capital's airport. In Soria a car does fewer and longer jobs than in any other province of the region, and the empty return is the variable that weighs most.

How does a job enter the portal, and how is it shared between cars so far apart?

The customer books with origin, destination, date and time, sees a fixed price before confirming and pays; the job enters the zone's queue and appears in the fleet's portal with the amount it will be paid. The fleet accepts it for one of its cars and chooses the driver, or leaves it for the first free driver of its own to take; each driver signs in to the app with their own credentials, sees only their own jobs and carries the navigation, the states and the trip sheet, generated before departure together with the filing with the national services register naming the assigned car and driver. In Soria, with the cars an hour apart from each other, notice is what rules: Barajas and Zaragoza runs are booked days ahead and let you decide the night before which car sleeps in Almazán and which in Ágreda. Turning a job down carries no penalty and there is no exclusivity: the fleet remains the operator and takes from the platform whatever suits it.

The province's rules travel with the job. At Soria and Medinaceli stations and at Barajas the pickup is always a customer with a booking, with their train or flight on the job, and the app follows delays; waiting at the taxi rank or soliciting on the platform is prohibited. During San Juan the centre of Soria is closed and the job carries the pickup point the town hall allows. In winter, Piqueras towards Logroño, Santa Inés towards the Laguna Negra and the fog on the Medinaceli plateau call for a margin: the job is confirmed the day before, departure is brought forward if there is ice and, if a road is closed, the customer is told through the app. At the Laguna Negra, in high season, the drop-off point is the one the access regulation allows, and at Numancia and the Río Lobos the return is booked with the outward trip, because there is no way to call for another car there.

How does the fleet get paid: card at booking, Stripe Connect and the commission invoice?

The customer pays by card when booking, on board if so agreed, or by bank transfer if it is a company on monthly invoicing, and the amount lands in the fleet's Stripe Connect account, not the platform's, with the commission published on the fleets page split out within the same charge. From Stripe to the fleet's bank the money moves on the schedule the fleet sets, daily, weekly or monthly, without passing through the platform. There is no joining fee, no monthly charge and no minimum: a month with no jobs costs nothing, and in a province where jobs are few and long that matters more than anywhere else. Non-payment is not the fleet's risk, because the job performed is settled even if the customer does not show, and late cancellations are paid under the published policy; an early-morning Barajas run cancelled at the last minute does not go unpaid.

Every fortnight, on the closing days the fleets page publishes, the statement arrives with every job, its amount, the commission withheld and the net, together with the platform's commission invoice to the fleet, numbered, with its base and its VAT, deductible, ready for the accountant. In the portal the fleet sees its assigned jobs, where each payment stands, the statements and the invoices without asking anyone. The price follows one of three paths, with their figures on the fleets page and not in this guide: the house fare, with a lower commission; the fleet's own fare once approved, with the published commission; or a bidding rule for the fleet's drivers. One isolated bad rating changes nothing; if a pattern repeats, there is a conversation before the assignment is touched, not after.

What is bidding for uncovered jobs, and why does it fit a province like Soria?

It is a pricing rule the fleet writes into its portal when bidding is switched on: base, target and floor per concept, standing or only on certain days and hours, adjustable per driver within the published limits, with the recommended value beside each box so nothing is made up. With the rule in place and the driver online in the app, the customer sees that car as one more option beside the house fare, at a price fixed before accepting, and chooses between the one that arrives first, the cheapest or the balance; the awarded amount is paid with the usual commission. With the driver offline, the bid does not count. If whoever had accepted cannot do it in the end, the customer's price is honoured and the platform's commission absorbs the difference. Without a rule nothing happens: the fleet carries on with the house fare or its own and the jobs from the zone's queue arrive just the same.

Soria is the province where this option makes most sense, because the villages are so far from each other that a job from Arcos de Jalón, Duruelo de la Sierra or Ólvega at shift time can be left with nobody to cover it: the portal shows the open jobs in the district and the fleet's rule decides at what price each car is offered, without anyone promising how many there will be in a February week in San Leonardo de Yagüe. It also fits the returns from Barajas with a customer coming back to the province, the early-morning departures from the Pinares villages and the San Juan pickups when the bus no longer runs. For a fleet of two or three cars the sensible thing is to start with airport transfers, the most predictable, and switch bidding on when the portal really shows uncovered jobs in its area.

What does the fleet software do, and what paperwork does joining require?

The fleet-management software keeps what in Soria is measured in kilometres: the expenses per vehicle, fuel, tyres and maintenance of cars that cover more road than in any other province of the region and that cross mountain passes; Barajas parking; the expiry dates of roadworthiness tests, insurance, authorisation, transport card and drivers' licences, with a warning before anything lapses; claims; the income from every platform the fleet works with; and the split with each driver according to their agreement. It produces the month's result per car, which is the figure that decides whether the Ágreda car pays off or whether it is better kept in the capital. It is included for partner fleets; a fleet that does not work with the platform can subscribe on its own, by the month. The platform as a tool, for a fee per licence per month and with no commission, is not on sale yet and the fleet software page describes it.

Joining requires valid VTC authorisations in the fleet's name, the vehicle records with roadworthiness test and registration document, passenger-cover insurance, the certificate of good standing with the tax agency and social security and a company bank account for Stripe Connect verification. The steps: an application from the fleets page with company name, tax ID, licences and area; paperwork and an agreement with the split and the scope; Stripe Connect onboarding, which decides when collecting can start; drivers and vehicles in the app with their expiry dates; and first jobs. Soria borders four regions and that matters: trips ending in Madrid, Zaragoza, Logroño or Pamplona are legal under a Castilla y León authorisation because the origin is in the province; what does not fit is stationing cars to pick up jobs originating outside the region beyond the share the ROTT allows.

Frequently asked questions

Sources

• Ministerio de Transportes · arrendamiento de vehículos con conductor (VTC): autorizaciones y Registro de Comunicaciones (consulted on 27 October 2026)
• BOE · Real Decreto-ley 13/2018, por el que se modifica la LOTT en materia de arrendamiento de vehículos con conductor (consulted on 27 October 2026)
• Adif · estaciones y servicios al viajero (consulted on 27 October 2026)
• Junta de Castilla y León · transporte: autorizaciones y normativa autonómica (consulted on 27 October 2026)