biztrac. BETA
COMPANY REGISTER PROFILE
921378963 ORG. NO. 2025 ACCOUNTS 7 SECTIONS
Active UPDATED 03.10.2026
Development of building projects

4U HOLDING AS

Org. no. 921378963 Limited company (AS) Nordre Follo Incorporated 2019 Active
Revenue 2025 NOK 0
Operating profit NOK −105,000
Equity NOK 1.3m
Incorporated 2019
Share capital NOK 40,000

Signals

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

4U HOLDING AS is registered as a limited company in Nordre Follo, Akershus with organisation number 921378963. The business is classified under development of building projects (NACE 68.120). The company was incorporated in 2019. Registered share capital is NOK 40,000, divided into 100 shares. The company's stated purpose is: “Investere, eie og videreutvikle eiendomsprosjekter.”. The most recent filed accounts, for the 2025 financial year, show NOK 0 in revenue and NOK −105,000 in operating profit.

Key figures · 2025

Revenue
NOK 0
Operating profit
NOK −105,000
▼ −1 %
Equity
NOK 1.3m
▼ −7 %
Est. value
NOK 1.2m

Financial health · 2025

Liquidity
13.21
Very good
Current assets ÷ current liabilities
Profitability
–
Not available
Return on total assets
Solidity
99.7%
Very good
Equity as a share of total capital

Who owns 4U HOLDING AS?

4U HOLDING AS has 4 registered shareholders:

All shareholders and roles →

Which companies does 4U HOLDING AS own?

4U HOLDING AS holds a stake in 1 company:

See the full ownership structure →

Frequently asked questions about 4U HOLDING AS

Who owns 4U HOLDING AS?

Andreas Unum is the largest registered owner, with 25.0%.

What is the revenue of 4U HOLDING AS?

4U HOLDING AS had revenue of NOK 0 in 2025.

Who is the general manager of 4U HOLDING AS?

Arnfinn Ingar Unum is registered as general manager of 4U HOLDING AS.

Where is 4U HOLDING AS based?

4U HOLDING AS has its business address in Kolbotn.

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.