BIZTRAC BETA
Landscape service activities

DALLAGER JORDBEARBEIDING AS

Org. no. 917363471 Limited company (AS) Narvik Incorporated 2016 Active
Ownership graph ↗
Revenue 2025 NOK 1.3m
Operating profit NOK 102,000
Equity NOK 134,000
Incorporated 2016
Share capital NOK 30,000

DALLAGER JORDBEARBEIDING AS is registered as a limited company in Narvik, Nordland with organisation number 917363471. The business is classified under landscape service activities (NACE 81.300). The company was incorporated in 2016. Registered share capital is NOK 30,000, divided into 30 shares. The company's stated purpose is: “Anleggsvirksomhet: Jordbearbeiding, vedlikehold og oppføring av grøntområder og parkanlegg. Produksjon av vekstmasse og matjord.”. The most recent filed accounts, for the 2025 financial year, show NOK 1.3m in revenue and NOK 102,000 in operating profit.

Key figures · 2025

Revenue
NOK 1.3m
Operating profit
NOK 102,000
Equity
NOK 134,000
Est. value
NOK 457,000

Financial health · 2025

Liquidity
0.81
Weak
Current assets ÷ current liabilities
Profitability
Not available
Return on total assets
Solidity
25.1%
Good
Equity as a share of total capital

Who owns DALLAGER JORDBEARBEIDING AS?

RAYMOND DALLAGER
DALLAGER JORDBEARBEIDING AS
NOK 1.3m rev. · NOK 102,000 profit

DALLAGER JORDBEARBEIDING AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about DALLAGER JORDBEARBEIDING AS

Who owns DALLAGER JORDBEARBEIDING AS?

RAYMOND DALLAGER is the largest registered owner, with 100.0%.

What is the revenue of DALLAGER JORDBEARBEIDING AS?

DALLAGER JORDBEARBEIDING AS had revenue of NOK 1.3m in 2025.

Who is the general manager of DALLAGER JORDBEARBEIDING AS?

Raymond Dallager is registered as general manager of DALLAGER JORDBEARBEIDING AS.

Where is DALLAGER JORDBEARBEIDING AS based?

DALLAGER JORDBEARBEIDING AS has its business address in Ankenes.

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.