BIZTRAC BETA
Computer programming activities

SENSORITA AS

Org. no. 825469702 Limited company (AS) Oslo Incorporated 2020 Active
Ownership graph ↗
Revenue 2024 NOK 8.8m
Operating profit NOK −1.4m
Equity NOK 39.6m
Incorporated 2020
Employees 7
Share capital NOK 50,000

Signals

1 flags
  • Driftsunderskudd 2024 Siste driftsresultat er negativt (−1,4 mill kr).

SENSORITA AS is registered as a limited company in Oslo, Oslo with organisation number 825469702. The business is classified under computer programming activities (NACE 62.100). The company was incorporated in 2020 and has 7 registered employees. Registered share capital is NOK 50,000, divided into 50131414 shares. The company's stated purpose is: “Software og sensorløsninger for avfallsbransjen.”. The most recent filed accounts, for the 2024 financial year, show NOK 8.8m in revenue and NOK −1.4m in operating profit.

Key figures · 2024

Revenue
NOK 8.8m
Operating profit
NOK −1.4m
Equity
NOK 39.6m
Est. value
NOK 32.8m

Financial health · 2025

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

Who owns SENSORITA AS?

LIEN ENGINEERING AS
SENSORITA AS
NOK 8.8m rev. · NOK −1.4m profit

SENSORITA AS has 20+ registered shareholders:

All shareholders and roles →

Which companies does SENSORITA AS own?

SENSORITA AS holds a stake in 1 company:

See the full ownership structure →

Frequently asked questions about SENSORITA AS

Who owns SENSORITA AS?

LIEN ENGINEERING AS is the largest registered owner, with 30.2%.

What is the revenue of SENSORITA AS?

SENSORITA AS had revenue of NOK 8.8m in 2024.

Who is the general manager of SENSORITA AS?

Ulrikke Erdal-Aase Lien is registered as general manager of SENSORITA AS.

Where is SENSORITA AS based?

SENSORITA AS has its business address in Oslo.

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.