BIZTRAC BETA
Rental and operating of own or leased real estate

FREDRIKSTAD BOLIGUTLEIE AS

Org. no. 922217947 Limited company (AS) Fredrikstad Incorporated 2018 Active
Ownership graph ↗
Revenue 2024 NOK 7.4m
Operating profit NOK 732,000
Equity NOK 15.7m
Incorporated 2018
Share capital NOK 374,000

FREDRIKSTAD BOLIGUTLEIE AS is registered as a limited company in Fredrikstad, Østfold with organisation number 922217947. The business is classified under rental and operating of own or leased real estate (NACE 68.200). The company was incorporated in 2018. Registered share capital is NOK 374,000, divided into 373916 shares. The company's stated purpose is: “Å eie, leie ut og drive fast eiendom, samt hva som naturlig står i forbindelse med dette.”. The most recent filed accounts, for the 2024 financial year, show NOK 7.4m in revenue and NOK 732,000 in operating profit.

Key figures · 2024

Revenue
NOK 7.4m
Operating profit
NOK 732,000
Equity
NOK 15.7m
Est. value
NOK 12.2m

Financial health · 2024

Liquidity
1.12
Satisfactory
Current assets ÷ current liabilities
Profitability
Not available
Return on total assets
Solidity
15.1%
Satisfactory
Equity as a share of total capital

Who owns FREDRIKSTAD BOLIGUTLEIE AS?

NAVESTA AS
FREDRIKSTAD BOLIGUTLEIE AS
NOK 7.4m rev. · NOK 732,000 profit

FREDRIKSTAD BOLIGUTLEIE AS has 1 registered shareholder:

All shareholders and roles →

Which companies does FREDRIKSTAD BOLIGUTLEIE AS own?

FREDRIKSTAD BOLIGUTLEIE AS holds a stake in 1 company:

See the full ownership structure →

Frequently asked questions about FREDRIKSTAD BOLIGUTLEIE AS

Who owns FREDRIKSTAD BOLIGUTLEIE AS?

NAVESTA AS is the largest registered owner, with 100.0%.

What is the revenue of FREDRIKSTAD BOLIGUTLEIE AS?

FREDRIKSTAD BOLIGUTLEIE AS had revenue of NOK 7.4m in 2024.

Where is FREDRIKSTAD BOLIGUTLEIE AS based?

FREDRIKSTAD BOLIGUTLEIE AS has its business address in Fredrikstad.

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.