BIZTRAC BETA
COMPANY REGISTER PROFILE
918066993 ORG. NO. 2025 ACCOUNTS 7 SECTIONS
Active UPDATED 02.09.2026
Technical testing and analysis

INNOSENSE AS

Org. no. 918066993 Limited company (AS) Lillestrøm Incorporated 2016 Active
Ownership graph ↗
Operating profit NOK −3,000
Equity NOK 130,000
Incorporated 2016
Share capital NOK 34,000

Signals

1 flags
  • Driftsunderskudd 2025 Siste driftsresultat er negativt (−3k kr).

INNOSENSE AS is registered as a limited company in Lillestrøm, Akershus with organisation number 918066993. The business is classified under technical testing and analysis (NACE 71.200). The company was incorporated in 2016. Registered share capital is NOK 34,000, divided into 34200 shares. The company's stated purpose is: “Å utvikle, produsere og selge en mikrosensor plattform som skal måle luftkvalitet.”.

Key figures · 2025

Operating profit
NOK −3,000
Equity
NOK 130,000
Est. value
NOK 211,000

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 INNOSENSE AS?

INNOSENSE AS has 4 registered shareholders:

All shareholders and roles →

Frequently asked questions about INNOSENSE AS

Who owns INNOSENSE AS?

STIFTELSEN NILU is the largest registered owner, with 70.2%.

Where is INNOSENSE AS based?

INNOSENSE AS has its business address in Kjeller.

Property

Business address c/o NILU AS Instituttveien 18, 2007 Kjeller
Cadastral unit 3205-26/21/0/0
Building Labratoriebygning · 1 unit

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.