BIZTRAC BETA
COMPANY REGISTER PROFILE
924375302 ORG. NO. 2025 ACCOUNTS 7 SECTIONS
Active UPDATED 15.06.2026
Development of building projects

DARBU EIENDOM AS

Org. no. 924375302 Limited company (AS) Oslo Incorporated 2019 Active
Ownership graph ↗
Revenue 2025 NOK 2.5m
Operating profit NOK 243,000
Equity NOK 595,000
Incorporated 2019
Share capital NOK 30,000

DARBU EIENDOM AS is registered as a limited company in Oslo, Oslo with organisation number 924375302. The business is classified under development of building projects (NACE 68.120). The company was incorporated in 2019. Registered share capital is NOK 30,000, divided into 100 shares. The company's stated purpose is: “Utvikling, forvaltning og drift av fast eiendom, herunder også kjøp og avhendelse, innleie, rehabilitering og utleie og all virksomhet som naturlig står i forbindelse med dette.”. The most recent filed accounts, for the 2025 financial year, show NOK 2.5m in revenue and NOK 243,000 in operating profit.

Key figures · 2025

Revenue
NOK 2.5m
Operating profit
NOK 243,000
Equity
NOK 595,000
Est. value
NOK 1.0m

Financial health · 2025

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

Who owns DARBU EIENDOM AS?

JIM DARBU
DARBU EIENDOM AS
NOK 2.5m rev. · NOK 243,000 profit

DARBU EIENDOM AS has 2 registered shareholders:

All shareholders and roles →

Frequently asked questions about DARBU EIENDOM AS

Who owns DARBU EIENDOM AS?

JIM DARBU is the largest registered owner, with 50.0%.

What is the revenue of DARBU EIENDOM AS?

DARBU EIENDOM AS had revenue of NOK 2.5m in 2025.

Who is the general manager of DARBU EIENDOM AS?

Jim Darbu is registered as general manager of DARBU EIENDOM AS.

Where is DARBU EIENDOM AS based?

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