BIZTRAC BETA
Other technical consultancy

INNREGULERER ERIKSSON AS

Org. no. 920190022 Limited company (AS) Lillestrøm Incorporated 2017 Active
Ownership graph ↗
Revenue 2024 NOK 1.3m
Operating profit NOK 12,000
Equity NOK 113,000
Incorporated 2017
Share capital NOK 30,000

INNREGULERER ERIKSSON AS is registered as a limited company in Lillestrøm, Akershus with organisation number 920190022. The business is classified under other technical consultancy (NACE 71.129). The company was incorporated in 2017. Registered share capital is NOK 30,000, divided into 100 shares. The company's stated purpose is: “Konsulentvirksomhet innen ventilasjons bransjen som inn regulering av ventilasjonssystem og annet som naturlig faller sammen med dette. Samt utføring av snekkertjenester innendørs og utendørs samt andre tjenester som naturlig faller inn under bransjen.”. The most recent filed accounts, for the 2024 financial year, show NOK 1.3m in revenue and NOK 12,000 in operating profit.

Key figures · 2024

Revenue
NOK 1.3m
Operating profit
NOK 12,000
Equity
NOK 113,000
Est. value
NOK 139,000

Financial health · 2024

Liquidity
0.54
Weak
Current assets ÷ current liabilities
Profitability
Not available
Return on total assets
Solidity
18.4%
Good
Equity as a share of total capital

Who owns INNREGULERER ERIKSSON AS?

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

Frequently asked questions about INNREGULERER ERIKSSON AS

What is the revenue of INNREGULERER ERIKSSON AS?

INNREGULERER ERIKSSON AS had revenue of NOK 1.3m in 2024.

Who is the general manager of INNREGULERER ERIKSSON AS?

Sonny Harald Andréas Eriksson is registered as general manager of INNREGULERER ERIKSSON AS.

Where is INNREGULERER ERIKSSON AS based?

INNREGULERER ERIKSSON AS has its business address in Fetsund.

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

Report a problem

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