BIZTRAC BETA
Manufacture of other builders' carpentry and joinery

AGDER ELEMENT AS

Org. no. 928883930 Limited company (AS) Farsund Incorporated 2022 Active
Ownership graph ↗
Revenue 2024 NOK 14.7m
Operating profit NOK 587,000
Equity NOK 1.0m
Incorporated 2022
Employees 19
Share capital NOK 450,000

Signals

1 flags
  • Ingen revisor Selskapet har ingen registrert revisor. Vanlig for små AS som har valgt bort revisjon, men verdt å merke seg.

AGDER ELEMENT AS is registered as a limited company in Farsund, Agder with organisation number 928883930. The business is classified under manufacture of other builders' carpentry and joinery (NACE 16.230). The company was incorporated in 2022 and has 19 registered employees. Registered share capital is NOK 450,000, divided into 300 shares. The company's stated purpose is: “Å utvikle og selge prefabrikkerte bygningselementer i tre i det nordiske markedet, samt oppgaver som hører naturlig sammen med dette m.m.”. The most recent filed accounts, for the 2024 financial year, show NOK 14.7m in revenue and NOK 587,000 in operating profit.

Key figures · 2024

Revenue
NOK 14.7m
Operating profit
NOK 587,000
Equity
NOK 1.0m
Est. value
NOK 2.3m

Financial health · 2024

Liquidity
1.06
Satisfactory
Current assets ÷ current liabilities
Profitability
Not available
Return on total assets
Solidity
13.5%
Satisfactory
Equity as a share of total capital

Who owns AGDER ELEMENT AS?

AGDER BOLIG GRUPPEN AS
AGDER ELEMENT AS
NOK 14.7m rev. · NOK 587,000 profit

AGDER ELEMENT AS has 2 registered shareholders:

All shareholders and roles →

Frequently asked questions about AGDER ELEMENT AS

Who owns AGDER ELEMENT AS?

AGDER BOLIG GRUPPEN AS is the largest registered owner, with 66.7%.

What is the revenue of AGDER ELEMENT AS?

AGDER ELEMENT AS had revenue of NOK 14.7m in 2024.

Where is AGDER ELEMENT AS based?

AGDER ELEMENT AS has its business address in Vanse.

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.