BIZTRAC BETA
COMPANY REGISTER PROFILE
990133948 ORG. NO. 2025 ACCOUNTS 7 SECTIONS
Active UPDATED 02.09.2026
Other specialised construction activities n.e.c.

BR ERIKSSON SOTEBYN AB

Org. no. 990133948 Norwegian division of foreign business enterprise (NUF) Indre Østfold Active
Ownership graph ↗
Revenue 2025 NOK 185,000
Operating profit NOK 151,000
Equity NOK 2.4m

BR ERIKSSON SOTEBYN AB is registered as a norwegian division of foreign business enterprise in Indre Østfold, Østfold with organisation number 990133948. The business is classified under other specialised construction activities n.e.c. (NACE 43.990). The most recent filed accounts, for the 2025 financial year, show NOK 185,000 in revenue and NOK 151,000 in operating profit.

Key figures · 2025

Revenue
NOK 185,000
Operating profit
NOK 151,000
Equity
NOK 2.4m
Est. value
NOK 1.5m

Financial health · 2025

Liquidity
Not available
Current assets ÷ current liabilities
Profitability
Not available
Return on total assets
Solidity
100.0%
Very good
Equity as a share of total capital

Who owns BR ERIKSSON SOTEBYN AB?

No shareholders are registered for BR ERIKSSON SOTEBYN AB in open Norwegian sources. Shareholder data exists mainly for limited companies (AS/ASA).

Frequently asked questions about BR ERIKSSON SOTEBYN AB

What is the revenue of BR ERIKSSON SOTEBYN AB?

BR ERIKSSON SOTEBYN AB had revenue of NOK 185,000 in 2025.

Where is BR ERIKSSON SOTEBYN AB based?

BR ERIKSSON SOTEBYN AB has its business address in Askim.

Property

Business address c/o Brænds Økonomi AS Møllegata 26, 1811 Askim
Cadastral unit 3118-53/816/0/0

16 companies are registered at this address.

The address this company is registered at, from the company register and matched against the cadastre. It does not say who owns the property — a company may be a tenant, and the address is often its accountant's. Source: Brønnøysundregistrene and © Kartverket.

Source: Biztrac.no · Data from the Brønnøysund Register Centre and the Norwegian Tax Administration · Last updated 02.09.2026.

Report a problem

Found a technical fault, or something wrong in the data? Tell us what happened.