Basically model is a class that maps to the data relation (table) and potentially bridge tables (e.g. for many to many relations).
you should keep your data model, the algorithms. For example if you write a spreadsheet application, you would keep the data structure of your spreadsheet. You would have the computation engine in your model, you would have the code to save and load your spreadsheet in your model. These model class could potentially be reused in other applications, for example if you have code to do compression of data.
so surely model is more helpful.
may be you can check multiple model in single view in following link
Editor, DotNetSpider MVM
Microsoft MVP 2014 [ASP.NET/IIS]