BIZTRAC BETA
Rental and operating of own or leased real estate

FB EIENDOM AS

Org. no. 917720371 Limited company (AS) Rakkestad Incorporated 2016 Active
Ownership graph ↗
Revenue 2024 NOK 3.5m
Operating profit NOK 482,000
Equity NOK −34,000
Incorporated 2016
Share capital NOK 100,000

Signals

1 flags
  • Negativ egenkapital 2024 Bokført egenkapital er negativ (−34k kr).

FB EIENDOM AS is registered as a limited company in Rakkestad, Østfold with organisation number 917720371. The business is classified under rental and operating of own or leased real estate (NACE 68.200). The company was incorporated in 2016. Registered share capital is NOK 100,000, divided into 100 shares. The company's stated purpose is: “Kjøp/salg av eiendommer, utleie av egen fast eiendom, inneha eierandeler i andre selskaper i beslektede bransjer.”. The most recent filed accounts, for the 2024 financial year, show NOK 3.5m in revenue and NOK 482,000 in operating profit.

Key figures · 2024

Revenue
NOK 3.5m
Operating profit
NOK 482,000
Equity
NOK −34,000
Est. value
NOK 3.7m

Financial health · 2024

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

Solidity capped at Weak because equity is below NOK 100,000.

Who owns FB EIENDOM AS?

PROKSIMAL AS
FB EIENDOM AS
NOK 3.5m rev. · NOK 482,000 profit

FB EIENDOM AS has 2 registered shareholders:

All shareholders and roles →

Frequently asked questions about FB EIENDOM AS

Who owns FB EIENDOM AS?

PROKSIMAL AS is the largest registered owner, with 50.0%.

What is the revenue of FB EIENDOM AS?

FB EIENDOM AS had revenue of NOK 3.5m in 2024.

Who is the general manager of FB EIENDOM AS?

Arild Sten Hovden is registered as general manager of FB EIENDOM AS.

Where is FB EIENDOM AS based?

FB EIENDOM AS has its business address in Rakkestad.

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.