BIZTRAC BETA
Manufacture of instruments and appliances for measuring, testing and navigation

BABYSENSOR AS

Org. no. 920230970 Limited company (AS) Larvik Incorporated 2018 Active
Ownership graph ↗
Revenue 2024 NOK 377,000
Operating profit NOK −5.0m
Equity NOK 14.7m
Incorporated 2018
Share capital NOK 137,000

Signals

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

BABYSENSOR AS is registered as a limited company in Larvik, Vestfold with organisation number 920230970. The business is classified under manufacture of instruments and appliances for measuring, testing and navigation (NACE 26.510). The company was incorporated in 2018. Registered share capital is NOK 137,000, divided into 13707716 shares. The company's stated purpose is: “Å produsere og selge sensorer og annet utstyr til måling av ulike faktorer som påvirker helse.”. The most recent filed accounts, for the 2024 financial year, show NOK 377,000 in revenue and NOK −5.0m in operating profit.

Key figures · 2024

Revenue
NOK 377,000
Operating profit
NOK −5.0m
Equity
NOK 14.7m
Est. value
NOK 17.3m

Financial health · 2024

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

Who owns BABYSENSOR AS?

FEVANGS HOLDING AS
BABYSENSOR AS
NOK 377,000 rev. · NOK −5.0m profit

BABYSENSOR AS has 20+ registered shareholders:

All shareholders and roles →

Frequently asked questions about BABYSENSOR AS

Who owns BABYSENSOR AS?

FEVANGS HOLDING AS is the largest registered owner, with 28.4%.

What is the revenue of BABYSENSOR AS?

BABYSENSOR AS had revenue of NOK 377,000 in 2024.

Who is the general manager of BABYSENSOR AS?

Rune Haraldsen is registered as general manager of BABYSENSOR AS.

Where is BABYSENSOR AS based?

BABYSENSOR AS has its business address in Tjodalyng.

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.