BIZTRAC BETA
Rental and operating of own or leased real estate

FETT EIENDOM AS

Org. no. 977483689 Limited company (AS) Oslo Incorporated 1997 Active
Ownership graph ↗
Revenue 2024 NOK 1.0m
Operating profit NOK 648,000
Equity NOK 540,000
Incorporated 1997
Share capital NOK 800,000

FETT EIENDOM AS is registered as a limited company in Oslo, Oslo with organisation number 977483689. The business is classified under rental and operating of own or leased real estate (NACE 68.200). The company was incorporated in 1997. Registered share capital is NOK 800,000. The company's stated purpose is: “Å kjøpe, eie, forvalte, utleie samt selge fast eiendom, aksjer, andeler og parter i andre selskaper samt drive handels-, konsulent-, investerings- og næringsvirksomhet av enhver art og deltakelse i andre selskaper med lignende virksomhet.”. The most recent filed accounts, for the 2024 financial year, show NOK 1.0m in revenue and NOK 648,000 in operating profit.

Key figures · 2024

Revenue
NOK 1.0m
Operating profit
NOK 648,000
Equity
NOK 540,000
Est. value
NOK 1.5m

Financial health · 2024

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

Who owns FETT EIENDOM AS?

HARRY FETT EFTF AS
FETT EIENDOM AS
NOK 1.0m rev. · NOK 648,000 profit

FETT EIENDOM AS has 1 registered shareholder:

All shareholders and roles →

Which companies does FETT EIENDOM AS own?

FETT EIENDOM AS holds a stake in 1 company:

See the full ownership structure →

Frequently asked questions about FETT EIENDOM AS

Who owns FETT EIENDOM AS?

HARRY FETT EFTF AS is the largest registered owner, with 100.0%.

What is the revenue of FETT EIENDOM AS?

FETT EIENDOM AS had revenue of NOK 1.0m in 2024.

Where is FETT EIENDOM AS based?

FETT 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.