BIZTRAC BETA
Other technical consultancy

INNOS AS

Org. no. 916707533 Limited company (AS) Lørenskog Incorporated 2015 Active
Ownership graph ↗
Revenue 2024 NOK 8.9m
Operating profit NOK 316,000
Equity NOK 675,000
Incorporated 2015
Share capital NOK 30,000

INNOS AS is registered as a limited company in Lørenskog, Akershus with organisation number 916707533. The business is classified under other technical consultancy (NACE 71.129). The company was incorporated in 2015. Registered share capital is NOK 30,000, divided into 2 shares. The company's stated purpose is: “Kommersiell utvikling, produksjon, salg og handel av utstyr og løsninger for bruk i fornybar-energi bransjen, og andre produkter og tjenester som naturlig faller sammen med dette. Herunder å delta i andre selskaper med lignende eller beslektet virksomhet, kjøp og salg av aksjer og eiendeler, eller på annen måte gjøre seg interessert i andre foretagender.”. The most recent filed accounts, for the 2024 financial year, show NOK 8.9m in revenue and NOK 316,000 in operating profit.

Key figures · 2024

Revenue
NOK 8.9m
Operating profit
NOK 316,000
Equity
NOK 675,000
Est. value
NOK 1.3m

Financial health · 2024

Liquidity
1.41
Satisfactory
Current assets ÷ current liabilities
Profitability
Not available
Return on total assets
Solidity
11.7%
Satisfactory
Equity as a share of total capital

Who owns INNOS AS?

TOMMY MIKAEL STRÖMBERG
INNOS AS
NOK 8.9m rev. · NOK 316,000 profit

INNOS AS has 2 registered shareholders:

All shareholders and roles →

Which companies does INNOS AS own?

INNOS AS holds a stake in 1 company:

See the full ownership structure →

Frequently asked questions about INNOS AS

Who owns INNOS AS?

TOMMY MIKAEL STRÖMBERG is the largest registered owner, with 50.0%.

What is the revenue of INNOS AS?

INNOS AS had revenue of NOK 8.9m in 2024.

Where is INNOS AS based?

INNOS AS has its business address in Rasta.

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.