BIZTRAC BETA
Manufacture of other builders' carpentry and joinery

NAGLESTAD BRUK AS

Org. no. 880408682 Limited company (AS) Lyngdal Incorporated 1998 Active
Ownership graph ↗
Revenue 2024 NOK 61.6m
Operating profit NOK 1.8m
Equity NOK 7.8m
Incorporated 1998
Employees 23
Share capital NOK 100,000

NAGLESTAD BRUK AS is registered as a limited company in Lyngdal, Agder with organisation number 880408682. The business is classified under manufacture of other builders' carpentry and joinery (NACE 16.230). The company was incorporated in 1998 and has 23 registered employees. Registered share capital is NOK 100,000, divided into 100 shares. The company's stated purpose is: “Produksjon og handel, samt annen virksomhet som naturlig står i forbindelse hermed, herunder å eie og drive fast eiendom, samt gjennom aksjetegning eller på annen måte.”. The most recent filed accounts, for the 2024 financial year, show NOK 61.6m in revenue and NOK 1.8m in operating profit.

Key figures · 2024

Revenue
NOK 61.6m
Operating profit
NOK 1.8m
Equity
NOK 7.8m
Est. value
NOK 10.8m

Financial health · 2024

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

Who owns NAGLESTAD BRUK AS?

OPTIMERA AS
NAGLESTAD BRUK AS
NOK 61.6m rev. · NOK 1.8m profit

NAGLESTAD BRUK AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about NAGLESTAD BRUK AS

Who owns NAGLESTAD BRUK AS?

OPTIMERA AS is the largest registered owner, with 100.0%.

What is the revenue of NAGLESTAD BRUK AS?

NAGLESTAD BRUK AS had revenue of NOK 61.6m in 2024.

Who is the general manager of NAGLESTAD BRUK AS?

Rolf Baardesø Hansen is registered as general manager of NAGLESTAD BRUK AS.

Where is NAGLESTAD BRUK AS based?

NAGLESTAD BRUK AS has its business address in Konsmo.

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.