Local Impact
Every scoop we log gets counted. Here's what we've cleared from Ocean & Monmouth County yards.
Post it. Brag a little. 🐾
A ready-to-share 1200×630 image with our live scoop count and pounds handled. Perfect for Instagram, Facebook, or your neighborhood group chat. Uses the industry-average 0.25 lb per scoop.
Sharing directly from the browser isn't supported here — download the PNG and post it anywhere.
1200×630 PNG. ~0.25 lb per scoop industry average.
That's ~0 lbs of waste kept out of NJ yards, storm drains, and streams.
By county
Ocean and Monmouth — where every Pupscaper visit happens.
Town leaderboard
Every town we cover, ranked by lifetime scoops cleared.
Counts include an initial launch baseline distributed across our service area and grow with every completed visit. Don't see your town? Ask us to add it.
Recent scoops, straight from the field
Every visit below is a real completed job logged by a Pupscaper technician in the last few days. We share the town, the scoop count, and whether proof photos were taken — never a name, address, or dog.
How we count scoops
We publish the same numbers our technicians log — nothing inflated, nothing hidden. Here's exactly what a "scoop" means, where the data comes from, and how often it refreshes.
One scoop = one pile of dog waste picked up and bagged during a visit. Technicians tap a +1 / +5 counter in the worker app after each pass of the yard and cannot mark a visit complete without logging a count.
Every completed visit ends with a timestamped photo of the cleaned yard and a gate-latch confirmation. The scoop count is saved next to those photos on the same job record — so the number and the proof travel together.
Counts are stored on the jobs table in our Lovable Cloud database and aggregated by a read-only function (get_scoop_stats). No customer names, addresses, or dog info are ever exposed by the public counter — only totals.
- • Technician log — every completed visit contributes its logged
scoop_count. - • Launch baseline — a fixed starting figure of 17,401 representing scoops cleared before we shipped this counter, distributed across our service area.
- • Town rollups — visits are matched to a town when the service address contains that town's name. Counts by county are simple sums of their towns.
- • Excluded — cancelled visits, blocked visits, and jobs still in progress.
- • Recorded instantly when a technician marks a visit complete in the field.
- • Public counter refreshes on page load and is cached for 5 minutes per visitor to keep the site fast.
- • Customer portal stats (your yard's impact) refresh every 60 seconds so your total moves right after we visit.
- • Snapshot time is stamped on every response — you can pull to refresh any time.
For each visit, yes — we count what we picked up. Site-wide totals include a small launch baseline so the counter reflects real historical service, not just the days since we shipped this page.
No. Completed visits are additive. Corrections (rare) are made on the underlying record, not by resetting the public number.
Never. The public and per-town counters are aggregate only. Customer-specific stats are gated behind sign-in and RLS.
By matching the service address to a covered town name. Ambiguous addresses (border neighborhoods, etc.) roll up under the town listed on the account.
See something off? Tell us — we'll double-check the record.