For the current version of Thunkable ✕ I think that @CBVG has the best approach: i.e. use a fixed number of components displayed however you like and use page-up and page-down buttons to populate those components with different subsets of your vehicles.
Sometime in the near future (hopefully in our next release, though it might be a little later) we will be releasing a set of advanced features that will allow you to dynamically create and place components. That will allow you to get closer to the kind of UI experience that you want. I’ll provide a warning, though, that these advanced blocks will be a bit harder to understand and use for developers that are not familiar with programming concepts.
In the longer term, we are working on an advanced data viewer component which will allow you to fairly simply map columns/fields in data sources (e.g. spreadsheets and eventually Web APIs) to properties of the component and give you very simple way to do the kind of thing that you want to do here.
We are also working on ways in which Thunkable ✕ users can themselves create components like the advanced data viewer component (using the advanced blocks mentioned earlier) and use these components in their own projects as well as share them with other users for use in their projects.
Hope this helps.