runsonwhat

BDS bilverkstad's tech stack

What does BDS bilverkstad use?

BDS bilverkstad (bds.se) uses at least 9 tools we can see from public records, including Google Analytics for analytics, WordPress for its website and SendGrid for email delivery. Last checked .

Size
11–50 employees
Based in
Haninge, Sweden
LinkedIn
Company page
Re-check liveVisit bds.se
Tools found
9
Categories
7
Layers
4 of 5
Last checked
Oct 2026

BDS bilverkstad's stack, layer by layer

Each tool links to the other companies we've found using it. The label says what kind of public trace gave it away.

Application

2 tools, what the product is built with

Frontend

Media & UI

Data & Observability

2 tools, what they measure and store

Analytics

Go-to-market

4 tools, how they find and keep customers

Website & CMS

Marketing

Ads & Pixels

Company Ops

1 tool, what the team runs on day to day

Email Delivery

Companies like BDS bilverkstad also use

Tools common among companies with a similar stack that we haven't found at BDS bilverkstad.

Companies with a stack like BDS bilverkstad's

Ranked by shared tools, with rare tools counting more.

BDS bilverkstad tech stack FAQ

What tools does BDS bilverkstad use?

We've found 9 tools at BDS bilverkstad (bds.se). Application: jQuery and Mapbox. Data & Observability: Google Analytics and Google Tag Manager. Go-to-market: Meta Pixel, Google Ads and WordPress. Company Ops: SendGrid. Last checked October 4, 2026.

What analytics tools does BDS bilverkstad use?

BDS bilverkstad uses Google Analytics and Google Tag Manager for analytics. We found Google Analytics through website code.

What CMS does BDS bilverkstad use?

BDS bilverkstad uses WordPress for its website. We found WordPress through website code.

Does BDS bilverkstad use Google Analytics?

Yes. We found Google Analytics at BDS bilverkstad through website code. Google Analytics is used by 89,943 companies we track.

How does runsonwhat know what BDS bilverkstad uses?

We read public traces only: BDS bilverkstad's DNS and email records, certificate logs, the code its website loads, and published subprocessor lists. A tool is listed only when a direct record backs it up. DNS is rechecked weekly and the website monthly.

We read public traces only: DNS and email records, certificate logs, website code and published subprocessor lists. A tool is listed when a direct record backs it up, and dropped when a recheck no longer finds it. Is this your company? See how to opt out.