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

KVERNSTUA UTLEIEBOLIGER AS

Org. no. 928908623 Limited company (AS) Lillestrøm Incorporated 2022 Active
Ownership graph ↗
Revenue 2025 NOK 1.8m
Operating profit NOK 1.1m
Equity NOK 234,000
Incorporated 2022
Share capital NOK 100,000

KVERNSTUA UTLEIEBOLIGER AS is registered as a limited company in Lillestrøm, Akershus with organisation number 928908623. The business is classified under rental and operating of own or leased real estate (NACE 68.200). The company was incorporated in 2022. Registered share capital is NOK 100,000, divided into 100 shares. The company's stated purpose is: “Eie, forvalte og leie ut boliger til vanskeligstilte etter avtale med kommunen samt annen virksomhet beslektet med dette.”. The most recent filed accounts, for the 2025 financial year, show NOK 1.8m in revenue and NOK 1.1m in operating profit.

Key figures · 2025

Revenue
NOK 1.8m
▲ +3 %
Operating profit
NOK 1.1m
▼ −10 %
Equity
NOK 234,000
▲ +0 %
Est. value
NOK 2.1m

Financial health · 2025

Liquidity
6.31
Very good
Current assets ÷ current liabilities
Profitability
3.5%
Weak
Return on total assets
Solidity
0.7%
Not satisfactory
Equity as a share of total capital

Who owns KVERNSTUA UTLEIEBOLIGER AS?

KVERNSTUA UTLEIEBOLIGER AS
NOK 1.8m rev. · NOK 1.1m profit

KVERNSTUA UTLEIEBOLIGER AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about KVERNSTUA UTLEIEBOLIGER AS

Who owns KVERNSTUA UTLEIEBOLIGER AS?

ØIE GRUPPEN AS is the largest registered owner, with 100.0%.

What is the revenue of KVERNSTUA UTLEIEBOLIGER AS?

KVERNSTUA UTLEIEBOLIGER AS had revenue of NOK 1.8m in 2025.

Where is KVERNSTUA UTLEIEBOLIGER AS based?

KVERNSTUA UTLEIEBOLIGER AS has its business address in Lillestrøm.

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.