BIZTRAC BETA
Beverage serving activities

KKJ INVEST AS

Org. no. 897239582 Limited company (AS) Modum Incorporated 2011 Active
Ownership graph ↗
Revenue 2025 NOK 682,000
Operating profit NOK 209,000
Equity NOK −1.3m
Incorporated 2011
Employees 9
Share capital NOK 105,000

Signals

1 flags
  • Negativ egenkapital 2025 Bokført egenkapital er negativ (−1,3 mill kr).

KKJ INVEST AS is registered as a limited company in Modum, Buskerud with organisation number 897239582. The business is classified under beverage serving activities (NACE 56.300). The company was incorporated in 2011 and has 9 registered employees. Registered share capital is NOK 105,000, divided into 105 shares. The company's stated purpose is: “Drift av pub og serveringssted med dertil tilhørende virksomhet.”. The most recent filed accounts, for the 2025 financial year, show NOK 682,000 in revenue and NOK 209,000 in operating profit.

Key figures · 2025

Revenue
NOK 682,000
Operating profit
NOK 209,000
Equity
NOK −1.3m
Est. value
NOK 845,000

Financial health · 2025

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

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

Who owns KKJ INVEST AS?

KNUT MYRHAUG STEFFERUD
KKJ INVEST AS
NOK 682,000 rev. · NOK 209,000 profit

KKJ INVEST AS has 3 registered shareholders:

All shareholders and roles →

Frequently asked questions about KKJ INVEST AS

Who owns KKJ INVEST AS?

KNUT MYRHAUG STEFFERUD is the largest registered owner, with 33.3%.

What is the revenue of KKJ INVEST AS?

KKJ INVEST AS had revenue of NOK 682,000 in 2025.

Who is the general manager of KKJ INVEST AS?

Jørre André Kjemperud is registered as general manager of KKJ INVEST AS.

Where is KKJ INVEST AS based?

KKJ INVEST AS has its business address in Vikersund.

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.