BIZTRAC BETA
Rental and operating of own or leased real estate

KVITHYLL EIERSELSKAP AS

Org. no. 927888424 Limited company (AS) Oslo Incorporated 2021 Active
Ownership graph ↗
Revenue 2025 NOK 29.7m
Operating profit NOK 29.6m
Equity NOK 60.9m
Incorporated 2021
Share capital NOK 200,000

Signals

1 flags
  • Ingen revisor Selskapet har ingen registrert revisor. Vanlig for små AS som har valgt bort revisjon, men verdt å merke seg.

KVITHYLL EIERSELSKAP AS is registered as a limited company in Oslo, Oslo with organisation number 927888424. The business is classified under rental and operating of own or leased real estate (NACE 68.200). The company was incorporated in 2021. Registered share capital is NOK 200,000, divided into 1000 shares. The company's stated purpose is: “Å eie fast eiendom og utleie av fast eiendom, eie aksjer i andre selskap, samt annen virksomhet som står i naturlig tilknytning til dette.”. The most recent filed accounts, for the 2025 financial year, show NOK 29.7m in revenue and NOK 29.6m in operating profit.

Key figures · 2025

Revenue
NOK 29.7m
Operating profit
NOK 29.6m
Equity
NOK 60.9m
Est. value
NOK 103.2m

Financial health · 2025

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

Who owns KVITHYLL EIERSELSKAP AS?

RAGDE EIENDOM AS
KVITHYLL EIERSELSKAP AS
NOK 29.7m rev. · NOK 29.6m profit

KVITHYLL EIERSELSKAP AS has 3 registered shareholders:

All shareholders and roles →

Frequently asked questions about KVITHYLL EIERSELSKAP AS

Who owns KVITHYLL EIERSELSKAP AS?

RAGDE EIENDOM AS is the largest registered owner, with 80.0%.

What is the revenue of KVITHYLL EIERSELSKAP AS?

KVITHYLL EIERSELSKAP AS had revenue of NOK 29.7m in 2025.

Where is KVITHYLL EIERSELSKAP AS based?

KVITHYLL EIERSELSKAP AS has its business address in Oslo.

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.