biztrac. BETA
COMPANY REGISTER PROFILE
925897884 ORG. NO. 2025 ACCOUNTS 11 SECTIONS
Active UPDATED 03.10.2026
Restaurant activities

KRESS AS

Org. no. 925897884 Limited company (AS) Vefsn Incorporated 2020 Active
Ownership graph ↗
Revenue 2025 NOK 6.7m
Operating profit NOK −304,000
Equity NOK −106,000
Incorporated 2020
Employees 10
Share capital NOK 200,000

Signals

2 flags
  • Negativ egenkapital 2025 Bokført egenkapital er negativ (−106k kr).
  • Driftsunderskudd 2025 Siste driftsresultat er negativt (−304k kr).

KRESS AS is registered as a limited company in Vefsn, Nordland with organisation number 925897884. The business is classified under restaurant activities (NACE 56.110). The company was incorporated in 2020 and has 10 registered employees. Registered share capital is NOK 200,000, divided into 200 shares. The company's stated purpose is: “Salg av næringsmidler og annet som naturlig faller sammen med dette.”. The most recent filed accounts, for the 2025 financial year, show NOK 6.7m in revenue and NOK −304,000 in operating profit.

Key figures · 2025

Revenue
NOK 6.7m
▼ −3 %
Operating profit
NOK −304,000
▼ −168 %
Equity
NOK −106,000
▼ −137 %

Financial health · 2025

Liquidity
0.78
Weak
Current assets ÷ current liabilities
Profitability
-26.6%
Not satisfactory
Return on total assets
Solidity
-11.5%
Weak
Equity as a share of total capital

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

Who owns KRESS AS?

KRESS AS has 5 registered shareholders:

All shareholders and roles →

Which companies does KRESS AS own?

KRESS AS holds a stake in 1 company:

See the full ownership structure →

Frequently asked questions about KRESS AS

Who owns KRESS AS?

KRESS AS is the largest registered owner, with 20.0%.

What is the revenue of KRESS AS?

KRESS AS had revenue of NOK 6.7m in 2025.

Where is KRESS AS based?

KRESS AS has its business address in Mosjøen.

Source: Biztrac.no · Data from the Brønnøysund Register Centre and the Norwegian Tax Administration · Last updated 03.10.2026.

Report a problem

Found a technical fault, or something wrong in the data? Tell us what happened.