BIZTRAC BETA
Business and other management consultancy activities

JOMANI STREAM AS

Org. no. 926016296 Limited company (AS) Bærum Incorporated 2020 Active
Ownership graph ↗
Revenue 2025 NOK 1.4m
Operating profit NOK 1.0m
Equity NOK −682,000
Incorporated 2020
Share capital NOK 30,000

Signals

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

JOMANI STREAM AS is registered as a limited company in Bærum, Akershus with organisation number 926016296. The business is classified under business and other management consultancy activities (NACE 70.200). The company was incorporated in 2020. Registered share capital is NOK 30,000, divided into 10000 shares. The company's stated purpose is: “Konsulent- og investeringsvirksomhet.”. The most recent filed accounts, for the 2025 financial year, show NOK 1.4m in revenue and NOK 1.0m in operating profit.

Key figures · 2025

Revenue
NOK 1.4m
Operating profit
NOK 1.0m
Equity
NOK −682,000
Est. value
NOK 4.7m

Financial health · 2025

Liquidity
3.36
Very good
Current assets ÷ current liabilities
Profitability
Not available
Return on total assets
Solidity
-168.6%
Weak
Equity as a share of total capital

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

Who owns JOMANI STREAM AS?

KRISTIAN HOGRENNING RASMUSSEN
JOMANI STREAM AS
NOK 1.4m rev. · NOK 1.0m profit

JOMANI STREAM AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about JOMANI STREAM AS

Who owns JOMANI STREAM AS?

KRISTIAN HOGRENNING RASMUSSEN is the largest registered owner, with 100.0%.

What is the revenue of JOMANI STREAM AS?

JOMANI STREAM AS had revenue of NOK 1.4m in 2025.

Who is the general manager of JOMANI STREAM AS?

Kristian Hogrenning Rasmussen is registered as general manager of JOMANI STREAM AS.

Where is JOMANI STREAM AS based?

JOMANI STREAM AS has its business address in Stabekk.

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.