BIZTRAC BETA
Rental and operating of own or leased real estate

FERSA EIENDOM AS

Org. no. 933915948 Limited company (AS) Alver Incorporated 2024 Active
Ownership graph ↗
Revenue 2025 NOK 0
Operating profit NOK −48,000
Equity NOK 5.0m
Incorporated 2024
Share capital NOK 5.0m

Signals

1 flags
  • Driftsunderskudd 2025 Siste driftsresultat er negativt (−48k kr).

FERSA EIENDOM AS is registered as a limited company in Alver, Vestland with organisation number 933915948. The business is classified under rental and operating of own or leased real estate (NACE 68.200). The company was incorporated in 2024. Registered share capital is NOK 5.0m, divided into 1000 shares. The company's stated purpose is: “Investere i eiendom.”. The most recent filed accounts, for the 2025 financial year, show NOK 0 in revenue and NOK −48,000 in operating profit.

Key figures · 2025

Revenue
NOK 0
Operating profit
NOK −48,000
Equity
NOK 5.0m
Est. value
NOK 4.2m

Financial health · 2025

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

Who owns FERSA EIENDOM AS?

CHRISTER FLØYSAND HOLDING AS
FERSA EIENDOM AS
NOK 0 rev. · NOK −48,000 profit

FERSA EIENDOM AS has 6 registered shareholders:

All shareholders and roles →

Which companies does FERSA EIENDOM AS own?

FERSA EIENDOM AS holds a stake in 1 company:

See the full ownership structure →

Frequently asked questions about FERSA EIENDOM AS

Who owns FERSA EIENDOM AS?

CHRISTER FLØYSAND HOLDING AS is the largest registered owner, with 70.0%.

What is the revenue of FERSA EIENDOM AS?

FERSA EIENDOM AS had revenue of NOK 0 in 2025.

Who is the general manager of FERSA EIENDOM AS?

Christer Fløysand is registered as general manager of FERSA EIENDOM AS.

Where is FERSA EIENDOM AS based?

FERSA EIENDOM AS has its business address in Frekhaug.

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.