BIZTRAC BETA
Construction of roads and motorways

AGDER VEIVEDLIKEHOLD AS

Org. no. 828744062 Limited company (AS) Åmli Incorporated 2022 Active
Ownership graph ↗
Revenue 2025 NOK 3.8m
Operating profit NOK 252,000
Equity NOK 1.6m
Incorporated 2022
Share capital NOK 500,000

AGDER VEIVEDLIKEHOLD AS is registered as a limited company in Åmli, Agder with organisation number 828744062. The business is classified under construction of roads and motorways (NACE 42.110). The company was incorporated in 2022. Registered share capital is NOK 500,000, divided into 1 shares. The company's stated purpose is: “Entreprenørtjenester innenfor bygg, anlegg og veivedlikehold, samt hva som naturlig hører sammen med dette. Selskapet kan eie aksjer/andeler i andre selskaper.”. The most recent filed accounts, for the 2025 financial year, show NOK 3.8m in revenue and NOK 252,000 in operating profit.

Key figures · 2025

Revenue
NOK 3.8m
Operating profit
NOK 252,000
Equity
NOK 1.6m
Est. value
NOK 1.8m

Financial health · 2025

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

Who owns AGDER VEIVEDLIKEHOLD AS?

BEST PÅ SKOG INVEST AS
AGDER VEIVEDLIKEHOLD AS
NOK 3.8m rev. · NOK 252,000 profit

AGDER VEIVEDLIKEHOLD AS has 2 registered shareholders:

All shareholders and roles →

Frequently asked questions about AGDER VEIVEDLIKEHOLD AS

Who owns AGDER VEIVEDLIKEHOLD AS?

BEST PÅ SKOG INVEST AS is the largest registered owner, with 66.0%.

What is the revenue of AGDER VEIVEDLIKEHOLD AS?

AGDER VEIVEDLIKEHOLD AS had revenue of NOK 3.8m in 2025.

Who is the general manager of AGDER VEIVEDLIKEHOLD AS?

Stian Espeland Finsrud is registered as general manager of AGDER VEIVEDLIKEHOLD AS.

Where is AGDER VEIVEDLIKEHOLD AS based?

AGDER VEIVEDLIKEHOLD AS has its business address in Selåsvatn.

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.