biztrac. BETA
COMPANY REGISTER PROFILE
922060770 ORG. NO. 2025 ACCOUNTS 8 SECTIONS
Active UPDATED 03.10.2026
Buying and selling of own real estate

FUN EIENDOM AS

Org. no. 922060770 Limited company (AS) Time Incorporated 2019 Active
Ownership graph ↗
Revenue 2025 NOK 1.7m
Operating profit NOK 1.1m
Equity NOK 3.5m
Incorporated 2019
Share capital NOK 33,000

Signals

1 flags
  • Nylig endring 2026-09-23 Adresseendring registrert 2026-09-23.

FUN EIENDOM AS is registered as a limited company in Time, Rogaland with organisation number 922060770. The business is classified under buying and selling of own real estate (NACE 68.110). The company was incorporated in 2019. Registered share capital is NOK 33,000, divided into 300 shares. The company's stated purpose is: “Kjøp, salg og utleie av egen fast eiendom og investering i selskaper innfor samme virksomhet.”. The most recent filed accounts, for the 2025 financial year, show NOK 1.7m in revenue and NOK 1.1m in operating profit.

Key figures · 2025

Revenue
NOK 1.7m
▲ +7 %
Operating profit
NOK 1.1m
▲ +11 %
Equity
NOK 3.5m
▼ −5 %
Est. value
NOK 4.0m

Financial health · 2025

Liquidity
0.16
Not satisfactory
Current assets ÷ current liabilities
Profitability
4.4%
Weak
Return on total assets
Solidity
13.7%
Satisfactory
Equity as a share of total capital

Who owns FUN EIENDOM AS?

FUN EIENDOM AS
NOK 1.7m rev. · NOK 1.1m profit

FUN EIENDOM AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about FUN EIENDOM AS

Who owns FUN EIENDOM AS?

FUN INVESTERING AS is the largest registered owner, with 100.0%.

What is the revenue of FUN EIENDOM AS?

FUN EIENDOM AS had revenue of NOK 1.7m in 2025.

Who is the general manager of FUN EIENDOM AS?

Fredrik Undheim is registered as general manager of FUN EIENDOM AS.

Where is FUN EIENDOM AS based?

FUN EIENDOM AS has its business address in Bryne.

Source: Biztrac.no · Data from the Brønnøysund Register Centre and the Norwegian Tax Administration · Last updated 03.10.2026.

Report a problem

Found a technical fault, or something wrong in the data? Tell us what happened.