biztrac. BETA
COMPANY REGISTER PROFILE
932686791 ORG. NO. 2025 ACCOUNTS 8 SECTIONS
Active UPDATED 03.10.2026
Landscape service activities

HANSEN MULTISERVICE AS

Org. no. 932686791 Limited company (AS) Tjeldsund Incorporated 2023 Active
Ownership graph ↗
Revenue 2025 NOK 1.0m
Operating profit NOK 404,000
Equity NOK 473,000
Incorporated 2023
Share capital NOK 30,000

HANSEN MULTISERVICE AS is registered as a limited company in Tjeldsund, Troms with organisation number 932686791. The business is classified under landscape service activities (NACE 81.300). The company was incorporated in 2023. Registered share capital is NOK 30,000, divided into 1053 shares. The company's stated purpose is: “Anleggsgartneri, snøbrøyting, ryddeoppdrag, grøftearbeid, rivning.”. The most recent filed accounts, for the 2025 financial year, show NOK 1.0m in revenue and NOK 404,000 in operating profit.

Key figures · 2025

Revenue
NOK 1.0m
▲ +110 %
Operating profit
NOK 404,000
▲ +112 %
Equity
NOK 473,000
▲ +239 %
Est. value
NOK 1.1m

Financial health · 2025

Liquidity
1.73
Good
Current assets ÷ current liabilities
Profitability
65.1%
Very good
Return on total assets
Solidity
54.8%
Very good
Equity as a share of total capital

Who owns HANSEN MULTISERVICE AS?

HANSEN MULTISERVICE AS
NOK 1.0m rev. · NOK 404,000 profit

HANSEN MULTISERVICE AS has 2 registered shareholders:

All shareholders and roles →

Frequently asked questions about HANSEN MULTISERVICE AS

Who owns HANSEN MULTISERVICE AS?

Martin Espen Hansen is the largest registered owner, with 95.1%.

What is the revenue of HANSEN MULTISERVICE AS?

HANSEN MULTISERVICE AS had revenue of NOK 1.0m in 2025.

Who is the general manager of HANSEN MULTISERVICE AS?

Martin Espen Hansen is registered as general manager of HANSEN MULTISERVICE AS.

Where is HANSEN MULTISERVICE AS based?

HANSEN MULTISERVICE AS has its business address in Kongsvik.

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.