BIZTRAC BETA
Rental and operating of own or leased real estate

KVENILD EIENDOM III AS

Org. no. 998303338 Limited company (AS) Trondheim Incorporated 2012 Active
Ownership graph ↗
Operating profit NOK −627,000
Equity NOK −1.5m
Incorporated 2012
Share capital NOK 1.0m

Signals

3 flags
  • Negativ egenkapital 2025 Bokført egenkapital er negativ (−1,5 mill kr).
  • Driftsunderskudd 2025 Siste driftsresultat er negativt (−627k kr).
  • Ingen revisor Selskapet har ingen registrert revisor. Vanlig for små AS som har valgt bort revisjon, men verdt å merke seg.

KVENILD EIENDOM III AS is registered as a limited company in Trondheim, Trøndelag with organisation number 998303338. The business is classified under rental and operating of own or leased real estate (NACE 68.200). The company was incorporated in 2012. Registered share capital is NOK 1.0m, divided into 1030 shares. The company's stated purpose is: “Erverv, planlegging og prosjektering, utbygging og drift av eiendom og bygg. Videre har selskapet til formål å organisere eller delta i tiltak eller selskap som har sammenheng med ovennevnte formål.”.

Key figures · 2025

Operating profit
NOK −627,000
Equity
NOK −1.5m

Financial health · 2025

Liquidity
0.43
Not satisfactory
Current assets ÷ current liabilities
Profitability
Not available
Return on total assets
Solidity
-10.8%
Weak
Equity as a share of total capital

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

Who owns KVENILD EIENDOM III AS?

TORGÅRD TOMT 2 AS
KVENILD EIENDOM III AS
· NOK −627,000 profit

KVENILD EIENDOM III AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about KVENILD EIENDOM III AS

Who owns KVENILD EIENDOM III AS?

TORGÅRD TOMT 2 AS is the largest registered owner, with 100.0%.

Where is KVENILD EIENDOM III AS based?

KVENILD EIENDOM III 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.