No, it's not a row total, as Steve noted. It's the number of seek operations since the stats for that index were created.
One query that reads, say 5,000 rows, might use 5000 different seeks to do that, if SQL chose to do the lookups that way. But it's still not directly a row count, as the access could be a "seek and scan", which does one seek but then reads multiple rows.
SQL DBA,SQL Server MVP(07, 08, 09) "Money can't buy you happiness." Maybe so, but it can make your unhappiness a LOT more comfortable!