BIZTRAC BETA
Development of building projects

KVENILD AREAL AS

Org. no. 984922795 Limited company (AS) Trondheim Incorporated 2002 Active
Ownership graph ↗
Revenue 2024 NOK 156,000
Operating profit NOK 69,000
Equity NOK −5.1m
Incorporated 2002
Share capital NOK 200,000

Signals

2 flags
  • Negativ egenkapital 2024 Bokført egenkapital er negativ (−5,1 mill kr).
  • Ingen revisor Selskapet har ingen registrert revisor. Vanlig for små AS som har valgt bort revisjon, men verdt å merke seg.

KVENILD AREAL AS is registered as a limited company in Trondheim, Trøndelag with organisation number 984922795. The business is classified under development of building projects (NACE 68.120). The company was incorporated in 2002. Registered share capital is NOK 200,000, divided into 2000 shares. The company's stated purpose is: “Erverv, utvikling og salg av fast eiendom.”. The most recent filed accounts, for the 2024 financial year, show NOK 156,000 in revenue and NOK 69,000 in operating profit.

Key figures · 2024

Revenue
NOK 156,000
Operating profit
NOK 69,000
Equity
NOK −5.1m
Est. value
NOK 473,000

Financial health · 2025

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

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

Who owns KVENILD AREAL AS?

TOMTEUTVIKLING HOLDING AS
KVENILD AREAL AS
NOK 156,000 rev. · NOK 69,000 profit

KVENILD AREAL AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about KVENILD AREAL AS

Who owns KVENILD AREAL AS?

TOMTEUTVIKLING HOLDING AS is the largest registered owner, with 100.0%.

What is the revenue of KVENILD AREAL AS?

KVENILD AREAL AS had revenue of NOK 156,000 in 2024.

Where is KVENILD AREAL AS based?

KVENILD AREAL AS has its business address in Trondheim.

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.