How carpooling really works in Morocco? An analysis of 1,004 ride posts
In the feed of a Moroccan Facebook carpool group, we recorded 1,004 ride posts on 10 September 2026: who offers seats, when people travel, which routes come up, and why finding the right post is so hard. Here is what they show, and what we want to do differently with Naveto.
994
unique posts analysed
1,004 recorded, 10 duplicates removed
1.28
driver offers for each passenger request
479 offers and 374 requests classified
30%
of posts give a specific time
45% of offers, 11% of requests
18%
of posts include a phone number
the rest is often arranged in comments
Method and limits
The source is the public group 'Covoiturage Maroc 'Yalahm3aya'', based in Rabat. On 10 September 2026 we recorded 1,004 top-level posts from its feed. After removing 10 duplicates, 994 posts remain, written by 686 distinct authors. The feed shows only relative ages ('3 h', '6 min'), so we cannot date the period covered precisely.
This is not a representative sample of Morocco. It is what the group's feed showed during one browsing session. Three limits matter most:
- Offer and request labels come from keywords in French, Darija and Arabic. We have not measured their error rate. 141 posts stay unclassified: greetings, feed bumps, off-topic posts.
- Requests written as comments are not counted, so the share of passenger requests is probably understated.
- A post that exists only as an image is not read. A city named only by its neighbourhood (for example Maarif) is not counted as a city either.
No names, phone numbers or identifiable quotes are reproduced in this article. The figures are counts.
Who offers, who searches
Of the 853 classified posts, 479 are driver offers (56%) and 374 are passenger requests (44%). The group leans towards supply, but not by much: for every five offers there are just under four requests.
The request share is probably understated, for the reason above. The two sides also post differently, and that shows most clearly in the times they give.
When people travel
Only 30% of posts give a specific time. Drivers are far more precise than passengers: 45% of offers state an hour, against 11% of requests. Half of all posts (51%) give neither an hour nor a part of the day.
| Time band | Mentions |
|---|---|
| 0:00 – 5:00 | 13 |
| 5:00 – 9:00 | 67 |
| 9:00 – 12:00 | 56 |
| 12:00 – 15:00 | 43 |
| 15:00 – 18:00 | 107 |
| 18:00 – 21:00 | 74 |
| 21:00 – 24:00 | 25 |
The most cited band is 3 pm to 6 pm, with 107 of 385 mentions (28%). Evening (74) and early morning (67) follow. When the time is vague, posts use parts of the day: 'sbah' or 'صباح' in 140 posts, 'l3chiya' or 'après-midi' in 61, 'blil' or 'soir' in 65.
On days, 326 posts (33%) name at least one. Friday leads, then Saturday and Sunday: those three days account for 52% of day mentions. Thursday and Monday follow with 46 and 45 mentions.
| Day | Mentions |
|---|---|
| Monday | 45 |
| Tuesday | 34 |
| Wednesday | 41 |
| Thursday | 46 |
| Friday | 66 |
| Saturday | 59 |
| Sunday | 58 |
Close to 45% of classified posts (383 of 853) mention today, tomorrow or tonight, in French, Darija or Arabic. Many trips are needed at short notice rather than planned weeks ahead.
The routes that come up most
648 posts (65%) name exactly two cities from our list. We count routes on those posts only, because their route is clear. The table shows the eight most cited routes; totals include unclassified posts.
| Route | Total | Offers | Requests |
|---|---|---|---|
| Agadir – Casablanca | 82 | 39 | 37 |
| Agadir – Marrakech | 51 | 32 | 8 |
| Casablanca – Marrakech | 39 | 21 | 15 |
| Marrakech – Rabat | 26 | 16 | 8 |
| Agadir – Rabat | 25 | 6 | 15 |
| Béni Mellal – Casablanca | 19 | 15 | 4 |
| Casablanca – Rabat | 18 | 12 | 5 |
| Casablanca – Tangier | 18 | 7 | 8 |
Agadir – Casablanca is the most cited route, with an almost even split between offers (39) and requests (37). Agadir – Marrakech is where offers outnumber requests most in the table: 32 offers for 8 requests. Agadir – Rabat is the reverse: 15 requests for 6 offers.
Casablanca – Rabat is probably undercounted here, most likely because office navettes are described by neighbourhood rather than by city. Routes in the table that have a page on Naveto link to it. Each page gives the distance and the suggested price per seat.
Regular trips
22 posts (2%) contain a repeat pattern: 'every day', 'Monday to Friday', 'navette'. Twelve are requests. These trips exist, but Facebook has no simple way to save them once and for all.
The more visible pattern is repetition by drivers. 31 accounts post at least four times each; together they account for 164 posts (16.5%). They repost the same route several times. The trip is regular, but it has to be reposted by hand.
By contrast, 515 of the 686 authors posted only once.
Price and contact
Price is almost absent from the posts: 6 of 994 (under 1%) state an amount. It is discussed in comments or private messages, which are not in our recording.
A phone number appears in about one post in five (18%), mostly in offers (28% of offers, against 5% of requests). We count Moroccan numbers starting with 05, 06 or 07, even when they are stuck to another word in the text.
Naveto shows a suggested price per route, calculated from distance. It does not rely on these posts, and it does not replace an agreement between driver and passenger.
Why finding a seat is so hard on Facebook
The numbers do not tell the whole story, but they explain the friction drivers and passengers describe. Five stand out.
- 01A vague time against a precise one
The driver writes '5:45 pm', the passenger writes 'l3chiya'. For the two to meet, a time window has to be compared with a clock time. A feed cannot do that.
- 02Half the posts give no time at all
Without an hour or a part of the day, you cannot tell whether a post fits your need until you have read it in full and replied.
- 03Coordination happens elsewhere
A phone number appears in only 18% of posts. The rest of the exchange happens in comments and private messages, which the feed does not sort.
- 04The same trips keep coming back
Some accounts repost the same trip every day, and bumps push one-off requests out of view. The feed is ranked by Facebook, not by your trip.
- 05One city, several spellings
In our recording, Casablanca appears as 'Casa', 'Casablanca', 'كازا' and 'Dar lbida'. A search has to recognise all of them.
What Naveto changes, and what is still to build
Naveto is not open yet. There is no bookable ride and no online payment today. Joining the waitlist means you are told at launch. Here is what is planned, then what this analysis adds to the list.
Planned for launch
- A listing that brings together the route, the time, the number of free seats and the cost share.
- Search by departure, destination and date.
- A profile with a verified phone number, so people can reach each other without hunting for the number in comments.
- Notifications for a new trip that matches your request, for a confirmed seat, or for the next day's navette.
- A regular trip: keep your seat from one day to the next, and release it on days you do not travel.
Ideas from this analysis, not built yet
- Search with a time window, such as 'morning' or '3 pm – 6 pm', rather than an exact hour.
- Recognise the different spellings of one city name, in French, Darija and Arabic.
What we take from this
Carpooling already exists in Morocco: 686 people posted in a single group. The problem is not a lack of people. It is finding the right post at the right time, and agreeing on the details without a long chain of comments. That is what Naveto is meant to solve.
Published 10 October 2026
Get notified at launch
Naveto is not open yet. Leave your contact to be notified, and tell us whether you are looking for a seat or offering seats.
Joining the waitlist does not guarantee you will find a ride: that depends on the trips offered.