BIZTRAC BETA
Sewerage

AGDER SERVICE & MONTASJE AS

Org. no. 914577802 Limited company (AS) Lyngdal Incorporated 2014 Active
Ownership graph ↗
Revenue 2024 NOK 1.3m
Operating profit NOK 68,000
Equity NOK 1.3m
Incorporated 2014
Share capital NOK 30,000

AGDER SERVICE & MONTASJE AS is registered as a limited company in Lyngdal, Agder with organisation number 914577802. The business is classified under sewerage (NACE 37.000). The company was incorporated in 2014. Registered share capital is NOK 30,000, divided into 2000 shares. The company's stated purpose is: “Drive med salg, service og vedlikehold av VVS-anlegg og andre produkter/tjenester som naturlig hører sammen med dette, herunder å delta i andre selskap med lignende virksomhet, og kjøp og salg av aksjer eller på annen måte gjøre seg interessert i andre foretak. Selskapet kan også drive salg av barneklær, leker og sko.”. The most recent filed accounts, for the 2024 financial year, show NOK 1.3m in revenue and NOK 68,000 in operating profit.

Key figures · 2024

Revenue
NOK 1.3m
Operating profit
NOK 68,000
Equity
NOK 1.3m
Est. value
NOK 995,000

Financial health · 2024

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

Who owns AGDER SERVICE & MONTASJE AS?

HAAKON FALKUM
AGDER SERVICE & MONTASJE AS
NOK 1.3m rev. · NOK 68,000 profit

AGDER SERVICE & MONTASJE AS has 2 registered shareholders:

All shareholders and roles →

Frequently asked questions about AGDER SERVICE & MONTASJE AS

Who owns AGDER SERVICE & MONTASJE AS?

HAAKON FALKUM is the largest registered owner, with 50.0%.

What is the revenue of AGDER SERVICE & MONTASJE AS?

AGDER SERVICE & MONTASJE AS had revenue of NOK 1.3m in 2024.

Where is AGDER SERVICE & MONTASJE AS based?

AGDER SERVICE & MONTASJE AS has its business address in Lyngdal.

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.