BIZTRAC BETA
Rental and operating of own or leased real estate

DUL SEL AS

Org. no. 919885254 Limited company (AS) Haugesund Incorporated 2017 Active
Ownership graph ↗
Revenue 2024 NOK 1.6m
Operating profit NOK 1.3m
Equity NOK −348,000
Incorporated 2017
Share capital NOK 2.0m

Signals

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

DUL SEL AS is registered as a limited company in Haugesund, Rogaland with organisation number 919885254. The business is classified under rental and operating of own or leased real estate (NACE 68.200). The company was incorporated in 2017. Registered share capital is NOK 2.0m, divided into 20 shares. The company's stated purpose is: “Investering og drift av egen fast eiendom, samt det som naturlig står i forbindelse med dette, herunder å delta i andre selskaper med tilsvarende virksomhet.”. The most recent filed accounts, for the 2024 financial year, show NOK 1.6m in revenue and NOK 1.3m in operating profit.

Key figures · 2024

Revenue
NOK 1.6m
Operating profit
NOK 1.3m
Equity
NOK −348,000
Est. value
NOK 8.6m

Financial health · 2024

Liquidity
7.76
Very good
Current assets ÷ current liabilities
Profitability
Not available
Return on total assets
Solidity
-2.4%
Weak
Equity as a share of total capital

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

Who owns DUL SEL AS?

BJARTE BRENDSDAL
DUL SEL AS
NOK 1.6m rev. · NOK 1.3m profit

DUL SEL AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about DUL SEL AS

Who owns DUL SEL AS?

BJARTE BRENDSDAL is the largest registered owner, with 100.0%.

What is the revenue of DUL SEL AS?

DUL SEL AS had revenue of NOK 1.6m in 2024.

Who is the general manager of DUL SEL AS?

Bjarte Brendsdal is registered as general manager of DUL SEL AS.

Where is DUL SEL AS based?

DUL SEL AS has its business address in Haugesund.

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.