BIZTRAC BETA
Rental and operating of own or leased real estate

FJELDBERG EIENDOM AS

Org. no. 931152769 Limited company (AS) Oslo Incorporated 2023 Active
Ownership graph ↗
Revenue 2024 NOK 329,000
Operating profit NOK 207,000
Equity NOK 17,000
Incorporated 2023
Share capital NOK 30,000

FJELDBERG EIENDOM AS is registered as a limited company in Oslo, Oslo with organisation number 931152769. The business is classified under rental and operating of own or leased real estate (NACE 68.200). The company was incorporated in 2023. Registered share capital is NOK 30,000, divided into 30000 shares. The company's stated purpose is: “Kjøp, salg og utleie av eiendom og annet som naturlig sammenfaller med dette.”. The most recent filed accounts, for the 2024 financial year, show NOK 329,000 in revenue and NOK 207,000 in operating profit.

Key figures · 2024

Revenue
NOK 329,000
Operating profit
NOK 207,000
Equity
NOK 17,000
Est. value
NOK 192,000

Financial health · 2024

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

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

Who owns FJELDBERG EIENDOM AS?

FJELDBERG CONSULTING AS
FJELDBERG EIENDOM AS
NOK 329,000 rev. · NOK 207,000 profit

FJELDBERG EIENDOM AS has 3 registered shareholders:

All shareholders and roles →

Frequently asked questions about FJELDBERG EIENDOM AS

Who owns FJELDBERG EIENDOM AS?

FJELDBERG CONSULTING AS is the largest registered owner, with 33.3%.

What is the revenue of FJELDBERG EIENDOM AS?

FJELDBERG EIENDOM AS had revenue of NOK 329,000 in 2024.

Who is the general manager of FJELDBERG EIENDOM AS?

Thomas Fjeldberg is registered as general manager of FJELDBERG EIENDOM AS.

Where is FJELDBERG EIENDOM AS based?

FJELDBERG EIENDOM AS has its business address in Oslo.

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.