runsonwhat

Löfbergs Baltic's tech stack

What does Löfbergs Baltic use?

Löfbergs Baltic (lofbergs.lv) uses at least 10 tools we can see from public records, including Microsoft 365 for email and documents, Google Analytics for analytics, WordPress for its website and Cookiebot for security. Last checked .

Industry
Food Production
Size
11–50 employees
Based in
Sweden
Founded
1906
LinkedIn
Company page
Tools found
10
Categories
6
Layers
4 of 5
Last checked
Oct 2026

Löfbergs Baltic'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

1 tool, what the product is built with

Data & Observability

2 tools, what they measure and store

Go-to-market

5 tools, how they find and keep customers

Company Ops

2 tools, what the team runs on day to day

Security & Compliance

Löfbergs Baltic tech stack FAQ

What tools does Löfbergs Baltic use?

We've found 10 tools at Löfbergs Baltic (lofbergs.lv). Application: jQuery. Data & Observability: Google Analytics and Google Tag Manager. Go-to-market: WordPress, Google Ads and Yoast SEO. Company Ops: Microsoft 365 and Cookiebot. Last checked October 2, 2026.

What email provider does Löfbergs Baltic use?

Löfbergs Baltic uses Microsoft 365 for email and documents. We found Microsoft 365 through DNS verification records, email records and website code.

What analytics tools does Löfbergs Baltic use?

Löfbergs Baltic uses Google Analytics and Google Tag Manager for analytics. We found Google Analytics through website code.

What CMS does Löfbergs Baltic use?

Löfbergs Baltic uses WordPress, Yoast SEO and Shopify for its website. We found WordPress through website code.

Does Löfbergs Baltic use Microsoft 365?

Yes. We found Microsoft 365 at Löfbergs Baltic through DNS verification records, email records and website code. Microsoft 365 is used by 320,201 companies we track.

How does runsonwhat know what Löfbergs Baltic uses?

We read public traces only: Löfbergs Baltic'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.