BIZTRAC BETA
Rental and operating of own or leased real estate

DELFIN EIENDOM AS

Org. no. 912259161 Limited company (AS) Oslo Incorporated 2013 Active
Ownership graph ↗
Revenue 2025 NOK 314,000
Operating profit NOK 220,000
Equity NOK −50,000
Incorporated 2013
Share capital NOK 30,000

Signals

1 flags
  • Negativ egenkapital 2025 Bokført egenkapital er negativ (−50k kr).

DELFIN EIENDOM AS is registered as a limited company in Oslo, Oslo with organisation number 912259161. The business is classified under rental and operating of own or leased real estate (NACE 68.200). The company was incorporated in 2013. Registered share capital is NOK 30,000, divided into 300 shares. The company's stated purpose is: “Kjøp, salg og drift av fast eiendom. Kjøp og salg av aksjer og verdipapirer, samt deltagelse i andre selskaper gjennom andeler eller verdipapirer av ethvert slag.”. The most recent filed accounts, for the 2025 financial year, show NOK 314,000 in revenue and NOK 220,000 in operating profit.

Key figures · 2025

Revenue
NOK 314,000
Operating profit
NOK 220,000
Equity
NOK −50,000
Est. value
NOK 1.7m

Financial health · 2025

Liquidity
0.04
Not satisfactory
Current assets ÷ current liabilities
Profitability
Not available
Return on total assets
Solidity
-2.0%
Weak
Equity as a share of total capital

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

Who owns DELFIN EIENDOM AS?

REIDAR ALEXANDER VIGEN
DELFIN EIENDOM AS
NOK 314,000 rev. · NOK 220,000 profit

DELFIN EIENDOM AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about DELFIN EIENDOM AS

Who owns DELFIN EIENDOM AS?

REIDAR ALEXANDER VIGEN is the largest registered owner, with 100.0%.

What is the revenue of DELFIN EIENDOM AS?

DELFIN EIENDOM AS had revenue of NOK 314,000 in 2025.

Where is DELFIN EIENDOM AS based?

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