I want to sum every 7 rows in a worksheet and put the sum in different column & rows

calendar_today Asked Sep 9, 2010
thumb_up 12 upvotes
history Updated April 14, 2026

Direct Answer

In D12, put =SUM(OFFSET($B$7,(ROW()-12)*8,0,8,1)) and fill down column D as far as you want. Note that B7:B14 is really 8 rows, not 7. If you really want 7 rows (B7:B13), then…. This is a prose walkthrough, ranked #132nd of 303 by community upvote score, from 2010.


The Problem (Q-score 5, ranked #132nd of 303 in the Excel VBA archive)

The scenario as originally posted in 2010

I have never really used Excel before but this seems like it should be possible.

I have an ongoing document where I will be adding values every day, but what I want it to do for every 7 rows I want it to sum those values and add the sum of the 7 rows to a different column/row, e.g.,

Row B7:B14 Sum in D12
Row B15:B22 Sum in D13

And then when I start adding data into B23 I want it to add the sum to D14.

Why community consensus is tight on this one

Across 303 Excel VBA entries in the archive, the accepted answer here holds solid answer (above median) status — meaning voters are unusually aligned on the right fix.


The Verified Solution — solid answer (above median) (+12)

Verbal answer — walkthrough without a code block

Note: the verified answer is a prose walkthrough. If you need a runnable sample, check Excel VBA entries ranked in the top 10 of the same archive.

In D12, put

=SUM(OFFSET($B$7,(ROW()-12)*8,0,8,1))

and fill down column D as far as you want. Note that B7:B14 is really 8 rows, not 7. If you really want 7 rows (B7:B13), then change the two 8’s to 7’s in the formula.


When to Use It — vintage (14+ years old, pre-2013)

Ranked #132nd in its category — specialized fit

This pattern sits in the 96% tail relative to the top answer. Reach for it when your scenario closely matches the question title; otherwise browse the Excel VBA archive for a higher-consensus alternative.

What changed between 2010 and 2026

The answer is 16 years old. The Excel VBA object model has been stable across Office 2013, 2016, 2019, 2021, 365, and 2024/2026 LTSC, so the pattern still compiles. Changes that might affect you: 64-bit API declarations (use PtrSafe), blocked macros in downloaded files (Mark-of-the-Web), and the shift toward Office Scripts for web-first workflows.

help
Frequently Asked Questions

Is this above-median answer still worth copying?
expand_more

Answer score +12 vs the Excel VBA archive median ~4; this entry is solid. The score plus 5 supporting upvotes on the question itself (+5) means the asker and 11 subsequent voters all validated the approach.

The answer has no code block — how do I turn it into a snippet?
expand_more

Use the walkthrough above as a checklist, then open a top-10 Excel VBA archive entry for a concrete starting template you can adapt.

This answer is 16 years old. Is it still relevant in 2026?
expand_more

Published 2010, which is 16 year(s) before today’s Office 2026 build. The Excel VBA object model has had no breaking changes in that window. Three things to re-test: (1) blocked macros on downloaded files (Mark-of-the-Web), (2) 64-bit API declarations (PtrSafe, LongPtr), (3) any shift toward Office Scripts for web scenarios.

Which Excel VBA pattern ranks just above this one at #131?
expand_more

The pattern one rank above is “C++ library to load Excel (.xls) files”. If your use case overlaps, compare both before committing.

Data source: Community-verified Q&A snapshot. Q-score 5, Answer-score 12, original post 2010, ranked #132nd of 303 in the Excel VBA archive. Last regenerated April 14, 2026.