BIZTRAC BETA
Rental and operating of own or leased real estate

DYBING EIENDOM AS

Org. no. 965601309 Limited company (AS) Eigersund Incorporated 1992 Active
Ownership graph ↗
Revenue 2025 NOK 153,000
Operating profit NOK 73,000
Equity NOK 1.0m
Incorporated 1992
Share capital NOK 100,000

DYBING EIENDOM AS is registered as a limited company in Eigersund, Rogaland with organisation number 965601309. The business is classified under rental and operating of own or leased real estate (NACE 68.200). The company was incorporated in 1992. Registered share capital is NOK 100,000, divided into 100 shares. The company's stated purpose is: “Produksjon, service, handel, kjøp, salg, drift av fast eiendom, samt hva dermed måtte stå i forbindelse, samt deltakelse i andre foretagender av hvilken som helst art, herunder også deltagelse gjennom aksjeverv.”. The most recent filed accounts, for the 2025 financial year, show NOK 153,000 in revenue and NOK 73,000 in operating profit.

Key figures · 2025

Revenue
NOK 153,000
Operating profit
NOK 73,000
Equity
NOK 1.0m
Est. value
NOK 818,000

Financial health · 2025

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

Who owns DYBING EIENDOM AS?

JONE DYBING
DYBING EIENDOM AS
NOK 153,000 rev. · NOK 73,000 profit

DYBING EIENDOM AS has 2 registered shareholders:

All shareholders and roles →

Frequently asked questions about DYBING EIENDOM AS

Who owns DYBING EIENDOM AS?

JONE DYBING is the largest registered owner, with 50.0%.

What is the revenue of DYBING EIENDOM AS?

DYBING EIENDOM AS had revenue of NOK 153,000 in 2025.

Who is the general manager of DYBING EIENDOM AS?

Jone Dybing is registered as general manager of DYBING EIENDOM AS.

Where is DYBING EIENDOM AS based?

DYBING EIENDOM AS has its business address in Egersund.

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.