biztrac. BETA
COMPANY REGISTER PROFILE
996284735 ORG. NO. 2025 ACCOUNTS 9 SECTIONS
Active UPDATED 03.10.2026
Rental and operating of own or leased real estate

DEKKLOGISTIKK EIENDOM AS

Org. no. 996284735 Limited company (AS) Oslo Incorporated 2010 Active
Ownership graph ↗
Revenue 2025 NOK 10.2m
Operating profit NOK 4.5m
Equity NOK 19.1m
Incorporated 2010
Share capital NOK 1.0m

DEKKLOGISTIKK EIENDOM AS is registered as a limited company in Oslo, Oslo with organisation number 996284735. The business is classified under rental and operating of own or leased real estate (NACE 68.200). The company was incorporated in 2010. Registered share capital is NOK 1.0m, divided into 1000 shares. The company's stated purpose is: “Å investere i fast eiendom eller selskaper som eier fast eiendom, og alt som dermed står i forbindelse.”. The most recent filed accounts, for the 2025 financial year, show NOK 10.2m in revenue and NOK 4.5m in operating profit.

Former names: MERE SØRLANDET AS, INVESTORPROSJEKT 125 AS

Key figures · 2025

Revenue
NOK 10.2m
▲ +3 %
Operating profit
NOK 4.5m
▲ +7 %
Equity
NOK 19.1m
▲ +6 %
Est. value
NOK 16.8m

Financial health · 2025

Liquidity
0.44
Not satisfactory
Current assets ÷ current liabilities
Profitability
5.5%
Weak
Return on total assets
Solidity
19.4%
Good
Equity as a share of total capital

Who owns DEKKLOGISTIKK EIENDOM AS?

DEKKLOGISTIKK EIENDOM AS
NOK 10.2m rev. · NOK 4.5m profit

DEKKLOGISTIKK EIENDOM AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about DEKKLOGISTIKK EIENDOM AS

Who owns DEKKLOGISTIKK EIENDOM AS?

DISENÅ LOGISTIKKEIENDOM AS is the largest registered owner, with 100.0%.

What is the revenue of DEKKLOGISTIKK EIENDOM AS?

DEKKLOGISTIKK EIENDOM AS had revenue of NOK 10.2m in 2025.

Where is DEKKLOGISTIKK EIENDOM AS based?

DEKKLOGISTIKK 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 03.10.2026.

Report a problem

Found a technical fault, or something wrong in the data? Tell us what happened.