Group by and sum query on multiple columns
First and most obvious issue is usage of ToList(), it's not required and you force creation of multiple (and possibly big) lists moreover you're repeating almost same code again and again. Step by step:

var fpslist = db.FPSinformations.Where(x =&gt; x.Godown_Code == godownid);


Unless comparison operator for Godown_Code is broken then you shouldn't need to check for null (in case you may opt for ?. to avoid it). Also you don't need .ToList(), drop it. If you will execute such code inside a loop you may consider to move this outside the loop (to be sure more context is needed).

Now let's make a reusable function (and also avoid to create multiple anonymous types, it's a micro optimization but it also simplifies our code):

static IEnumerable&lt;Tuple&lt;TName, TCount&gt;&gt; CountByType&lt;T, TName, TCount&gt;(
    IEnumerable&lt;T&gt; list,
    Func&lt;T, TName&gt; nameSelector,
    Func&lt;IEnumerable&lt;T&gt;, TCount&gt; aggregator)
{
    return list.Where(x =&gt; Object.Equals(nameSelector(x), null) == false)
        .GroupBy(x =&gt; nameSelector(x))
        .Select(x =&gt; Tuple.Create(x.Key, aggregator(x)));
}


Now your code can be greatly simplified (I assumed you cannot change database columns otherwise everything can be even simpler, see last section of this answer). I also used generics because type of your columns is unknown.

    var data1 = CountByType(fpslist, 
        x =&gt; x.Ration_Card_Type1,
        x =&gt; x.Sum(y =&gt; y.Ration_Card_Count1));

    var data2 = CountByType(fpslist, 
        x =&gt; x.Ration_Card_Type2,
        x =&gt; x.Sum(y =&gt; y.Ration_Card_Count2));

   // Repeat for each set

   var result = data1
       .Concatenate(data2)
       .Concatenate(data3)
       .Concatenate(data4)
       .Concatenate(data5);


Note that from your code it seems you can have multiple rows with a value for Ration_Card_CountX. If you have just one row then all code will be greatly reduced. Here I used a Tuple&lt;T1, T2&gt; because I do not know exact types of your objects, you'd better use a proper class instead.

Note that you can consume result as-is (an enumeration) or materialize a list (don't forget this if data comes from DB and connection will be disposed, LINQ execution is deferred).


About DB

I do not know if you can change your database schema and I do not know exact layout of your data then this section may not apply in your case.

If your data is in the form:


Ration_Card_Type1   Ration_Card_Count1   Ration_Card_Type2   Ration_Card_Count2
Type1                                5   NULL                                 0
NULL                                 0   Type2                               11
Type1                               12   Type2                                3


Then you have to keep your actual code but I would suggest to do not map 1:1 column names with C# property names (conventions are pretty different) then Ration_Card_Type1 should be RationCardType1 (assuming you can't simply have Type1, Type2 and so on).

If, for example, you have data with this simplified layout:


Ration_Card_Type1   Ration_Card_Count1   Ration_Card_Type2   Ration_Card_Count2
Type1                                5   NULL                                 0
NULL                                 0   Type2                               11
Type1                               12   NULL                                 0


Then you may both optimize and simplify your DB (it will also impact code):


Type   Count
1          5
2         11
1         12


In that case all you need (assuming your C# entities maps 1:1 with DB columns):

var result = db.GroupBy(x =&gt; x.Type)
    .Select(x =&gt; new { Type = x.Key, Count = x.Sum(y =&gt; y.Count) });