BIZTRAC BETA
Research and experimental development on natural sciences and engineering

SLEEPICUS AS

Org. no. 913744470 Limited company (AS) Oslo Incorporated 2014 Active
Ownership graph ↗
Revenue 2025 NOK 99,000
Operating profit NOK 65,000
Equity NOK −15,000
Incorporated 2014
Share capital NOK 30,000

Signals

1 flags
  • Negativ egenkapital 2025 Bokført egenkapital er negativ (−15k kr).

SLEEPICUS AS is registered as a limited company in Oslo, Oslo with organisation number 913744470. The business is classified under research and experimental development on natural sciences and engineering (NACE 72.100). The company was incorporated in 2014. Registered share capital is NOK 30,000, divided into 10000 shares. The company's stated purpose is: “Konsulentvirksomhet, foredrag og tilknyttet virksomhet relatert til søvnforskning og søvnmedisin, herunder å eie andeler i selskap med lignende formål, samt generell investeringsvirksomhet.”. The most recent filed accounts, for the 2025 financial year, show NOK 99,000 in revenue and NOK 65,000 in operating profit.

Key figures · 2025

Revenue
NOK 99,000
Operating profit
NOK 65,000
Equity
NOK −15,000
Est. value
NOK 297,000

Financial health · 2025

Liquidity
0.85
Weak
Current assets ÷ current liabilities
Profitability
Not available
Return on total assets
Solidity
-17.2%
Weak
Equity as a share of total capital

Solidity capped at Weak because equity is below NOK 100,000.

Who owns SLEEPICUS AS?

HARALD HRUBOS-STRØM
SLEEPICUS AS
NOK 99,000 rev. · NOK 65,000 profit

SLEEPICUS AS has 2 registered shareholders:

All shareholders and roles →

Frequently asked questions about SLEEPICUS AS

Who owns SLEEPICUS AS?

HARALD HRUBOS-STRØM is the largest registered owner, with 50.0%.

What is the revenue of SLEEPICUS AS?

SLEEPICUS AS had revenue of NOK 99,000 in 2025.

Where is SLEEPICUS AS based?

SLEEPICUS 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.