BIZTRAC BETA
Rental and operating of own or leased real estate

DAN-STOCK NÆRINGSLOKALER AS

Org. no. 913654536 Limited company (AS) Oslo Incorporated 2014 Active
Ownership graph ↗
Revenue 2024 NOK 4.2m
Operating profit NOK 3.5m
Equity NOK 4.1m
Incorporated 2014
Share capital NOK 71,000

DAN-STOCK NÆRINGSLOKALER AS is registered as a limited company in Oslo, Oslo with organisation number 913654536. The business is classified under rental and operating of own or leased real estate (NACE 68.200). The company was incorporated in 2014. Registered share capital is NOK 71,000, divided into 71222 shares. The company's stated purpose is: “Å forestå erverv, drift, utvikling, utleie og forvaltning av faste eiendommer og alt som er forbundet med dette.”. The most recent filed accounts, for the 2024 financial year, show NOK 4.2m in revenue and NOK 3.5m in operating profit.

Key figures · 2024

Revenue
NOK 4.2m
Operating profit
NOK 3.5m
Equity
NOK 4.1m
Est. value
NOK 9.7m

Financial health · 2024

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

Who owns DAN-STOCK NÆRINGSLOKALER AS?

FOURXP AS
DAN-STOCK NÆRINGSLOKALER AS
NOK 4.2m rev. · NOK 3.5m profit

DAN-STOCK NÆRINGSLOKALER AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about DAN-STOCK NÆRINGSLOKALER AS

Who owns DAN-STOCK NÆRINGSLOKALER AS?

FOURXP AS is the largest registered owner, with 100.0%.

What is the revenue of DAN-STOCK NÆRINGSLOKALER AS?

DAN-STOCK NÆRINGSLOKALER AS had revenue of NOK 4.2m in 2024.

Who is the general manager of DAN-STOCK NÆRINGSLOKALER AS?

Steinar Paulsrud is registered as general manager of DAN-STOCK NÆRINGSLOKALER AS.

Where is DAN-STOCK NÆRINGSLOKALER AS based?

DAN-STOCK NÆRINGSLOKALER 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.