BIZTRAC BETA
Water collection, treatment and supply

KARIBRENNA VANNDRIFT AS

Org. no. 933714055 Limited company (AS) Ringerike Incorporated 2024 Active
Ownership graph ↗
Revenue 2025 NOK 20,000
Operating profit NOK −16,000
Equity NOK 8,000
Incorporated 2024
Share capital NOK 30,000

Signals

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

KARIBRENNA VANNDRIFT AS is registered as a limited company in Ringerike, Buskerud with organisation number 933714055. The business is classified under water collection, treatment and supply (NACE 36.000). The company was incorporated in 2024. Registered share capital is NOK 30,000, divided into 132 shares. The company's stated purpose is: “Drifte vannforsyning i Karibrenna hyttefelt i Ringerike kommune og annet som faller naturlig sammen med dette.”. The most recent filed accounts, for the 2025 financial year, show NOK 20,000 in revenue and NOK −16,000 in operating profit.

Key figures · 2025

Revenue
NOK 20,000
Operating profit
NOK −16,000
Equity
NOK 8,000
Est. value
NOK 17,000

Financial health · 2025

Liquidity
1.10
Satisfactory
Current assets ÷ current liabilities
Profitability
Not available
Return on total assets
Solidity
9.1%
Weak
Equity as a share of total capital

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

Who owns KARIBRENNA VANNDRIFT AS?

JAN IVAR JANSEN
KARIBRENNA VANNDRIFT AS
NOK 20,000 rev. · NOK −16,000 profit

KARIBRENNA VANNDRIFT AS has 3 registered shareholders:

All shareholders and roles →

Frequently asked questions about KARIBRENNA VANNDRIFT AS

Who owns KARIBRENNA VANNDRIFT AS?

JAN IVAR JANSEN is the largest registered owner, with 33.3%.

What is the revenue of KARIBRENNA VANNDRIFT AS?

KARIBRENNA VANNDRIFT AS had revenue of NOK 20,000 in 2025.

Where is KARIBRENNA VANNDRIFT AS based?

KARIBRENNA VANNDRIFT AS has its business address in Hønefoss.

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.