BIZTRAC BETA
Joinery installation

ARCTIC VEDLIKEHOLD AS

Org. no. 921496060 Limited company (AS) Målselv Incorporated 2018 Active
Ownership graph ↗
Revenue 2025 NOK 4.0m
Operating profit NOK 33,000
Equity NOK 980,000
Incorporated 2018
Share capital NOK 30,000

ARCTIC VEDLIKEHOLD AS is registered as a limited company in Målselv, Troms with organisation number 921496060. The business is classified under joinery installation (NACE 43.320). The company was incorporated in 2018. Registered share capital is NOK 30,000, divided into 100 shares. The company's stated purpose is: “Tak og fasade arbeid samt annen virksomhet som naturlig står i forbindelse med dette, herunder delta som aksjonær i annen relatert virksomhet.”. The most recent filed accounts, for the 2025 financial year, show NOK 4.0m in revenue and NOK 33,000 in operating profit.

Key figures · 2025

Revenue
NOK 4.0m
Operating profit
NOK 33,000
Equity
NOK 980,000
Est. value
NOK 536,000

Financial health · 2025

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

Who owns ARCTIC VEDLIKEHOLD AS?

ARKTISK HOLDING AS
ARCTIC VEDLIKEHOLD AS
NOK 4.0m rev. · NOK 33,000 profit

ARCTIC VEDLIKEHOLD AS has 1 registered shareholder:

All shareholders and roles →

Group structure

ARCTIC VEDLIKEHOLD AS er morselskap for 2 datterselskaper:

Frequently asked questions about ARCTIC VEDLIKEHOLD AS

Who owns ARCTIC VEDLIKEHOLD AS?

ARKTISK HOLDING AS is the largest registered owner, with 100.0%.

What is the revenue of ARCTIC VEDLIKEHOLD AS?

ARCTIC VEDLIKEHOLD AS had revenue of NOK 4.0m in 2025.

Who is the general manager of ARCTIC VEDLIKEHOLD AS?

Edgaras Alsys is registered as general manager of ARCTIC VEDLIKEHOLD AS.

Where is ARCTIC VEDLIKEHOLD AS based?

ARCTIC VEDLIKEHOLD AS has its business address in Moen.

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.