BIZTRAC BETA
Accounting and bookkeeping

FREDRIKSTAD BOLIGFORVALTNING AS

Org. no. 926317520 Limited company (AS) Fredrikstad Incorporated 2020 Active
Ownership graph ↗
Revenue 2024 NOK 897,000
Operating profit NOK 47,000
Equity NOK 130,000
Incorporated 2020
Share capital NOK 30,000

Signals

1 flags
  • Nylig endring 2026-04-27 Adresseendring registrert 2026-04-27.

FREDRIKSTAD BOLIGFORVALTNING AS is registered as a limited company in Fredrikstad, Østfold with organisation number 926317520. The business is classified under accounting and bookkeeping (NACE 69.202). The company was incorporated in 2020. Registered share capital is NOK 30,000, divided into 300 shares. The company's stated purpose is: “Regnskapsførsel, fakturering, økonomisk rådgivning, forretningsførsel samt det som naturlig står i forbindelse med dette.”. The most recent filed accounts, for the 2024 financial year, show NOK 897,000 in revenue and NOK 47,000 in operating profit.

Key figures · 2024

Revenue
NOK 897,000
Operating profit
NOK 47,000
Equity
NOK 130,000
Est. value
NOK 308,000

Financial health · 2024

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

Who owns FREDRIKSTAD BOLIGFORVALTNING AS?

PARAGGI AS
FREDRIKSTAD BOLIGFORVALTNING AS
NOK 897,000 rev. · NOK 47,000 profit

FREDRIKSTAD BOLIGFORVALTNING AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about FREDRIKSTAD BOLIGFORVALTNING AS

Who owns FREDRIKSTAD BOLIGFORVALTNING AS?

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

What is the revenue of FREDRIKSTAD BOLIGFORVALTNING AS?

FREDRIKSTAD BOLIGFORVALTNING AS had revenue of NOK 897,000 in 2024.

Where is FREDRIKSTAD BOLIGFORVALTNING AS based?

FREDRIKSTAD BOLIGFORVALTNING AS has its business address in Manstad.

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.