BIZTRAC BETA
Site preparation

HANSEN DRIFT OG VEDLIKEHOLD AS

Org. no. 928775364 Limited company (AS) Moss Incorporated 2022 Active
Ownership graph ↗
Revenue 2025 NOK 3.6m
Operating profit NOK 320,000
Equity NOK 914,000
Incorporated 2022
Share capital NOK 150,000

HANSEN DRIFT OG VEDLIKEHOLD AS is registered as a limited company in Moss, Østfold with organisation number 928775364. The business is classified under site preparation (NACE 43.120). The company was incorporated in 2022. Registered share capital is NOK 150,000, divided into 100 shares. The company's stated purpose is: “Snøbrøyting, strøing, graving, tilkjøring og bortkjøring av masser, grunnarbeid, drenering og trefelling.”. The most recent filed accounts, for the 2025 financial year, show NOK 3.6m in revenue and NOK 320,000 in operating profit.

Key figures · 2025

Revenue
NOK 3.6m
Operating profit
NOK 320,000
Equity
NOK 914,000
Est. value
NOK 1.6m

Financial health · 2024

Liquidity
1.14
Satisfactory
Current assets ÷ current liabilities
Profitability
Not available
Return on total assets
Solidity
72.6%
Very good
Equity as a share of total capital

Who owns HANSEN DRIFT OG VEDLIKEHOLD AS?

ELDAR HANSEN
HANSEN DRIFT OG VEDLIKEHOLD AS
NOK 3.6m rev. · NOK 320,000 profit

HANSEN DRIFT OG VEDLIKEHOLD AS has 2 registered shareholders:

All shareholders and roles →

Frequently asked questions about HANSEN DRIFT OG VEDLIKEHOLD AS

Who owns HANSEN DRIFT OG VEDLIKEHOLD AS?

ELDAR HANSEN is the largest registered owner, with 90.0%.

What is the revenue of HANSEN DRIFT OG VEDLIKEHOLD AS?

HANSEN DRIFT OG VEDLIKEHOLD AS had revenue of NOK 3.6m in 2025.

Who is the general manager of HANSEN DRIFT OG VEDLIKEHOLD AS?

Eldar Hansen is registered as general manager of HANSEN DRIFT OG VEDLIKEHOLD AS.

Where is HANSEN DRIFT OG VEDLIKEHOLD AS based?

HANSEN DRIFT OG VEDLIKEHOLD AS has its business address in Moss.

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.