biztrac. BETA
COMPANY REGISTER PROFILE
925161128 ORG. NO. 2025 ACCOUNTS 8 SECTIONS
Active UPDATED 03.10.2026
Rental and operating of own or leased real estate

KVERNENG AS

Org. no. 925161128 Limited company (AS) Vestby Incorporated 2020 Active
Revenue 2025 NOK 383,000
Operating profit NOK −14,000
Equity NOK 7,000
Incorporated 2020
Share capital NOK 30,000

Signals

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

KVERNENG AS is registered as a limited company in Vestby, Akershus with organisation number 925161128. The business is classified under rental and operating of own or leased real estate (NACE 68.200). The company was incorporated in 2020. Registered share capital is NOK 30,000, divided into 30000 shares. The company's stated purpose is: “Eiendom.”. The most recent filed accounts, for the 2025 financial year, show NOK 383,000 in revenue and NOK −14,000 in operating profit.

Key figures · 2025

Revenue
NOK 383,000
▼ −8 %
Operating profit
NOK −14,000
▼ −180 %
Equity
NOK 7,000
▼ −66 %
Est. value
NOK 580,000

Financial health · 2025

Liquidity
1.05
Satisfactory
Current assets ÷ current liabilities
Profitability
-8.8%
Not satisfactory
Return on total assets
Solidity
4.7%
Weak
Equity as a share of total capital

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

Who owns KVERNENG AS?

KVERNENG AS
NOK 383,000 rev. · NOK −14,000 profit

KVERNENG AS has 2 registered shareholders:

All shareholders and roles →

Frequently asked questions about KVERNENG AS

Who owns KVERNENG AS?

Marit Jensvold Kverneng is the largest registered owner, with 50.0%.

What is the revenue of KVERNENG AS?

KVERNENG AS had revenue of NOK 383,000 in 2025.

Who is the general manager of KVERNENG AS?

Hans Petter Kverneng is registered as general manager of KVERNENG AS.

Where is KVERNENG AS based?

KVERNENG AS has its business address in Son.

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.