BIZTRAC BETA
Rental and operating of own or leased real estate

NAGLESTAD BRUK EIENDOM AS

Org. no. 927436027 Limited company (AS) Lyngdal Incorporated 2021 Active
Ownership graph ↗
Revenue 2025 NOK 1.7m
Operating profit NOK 848,000
Equity NOK 3.9m
Incorporated 2021
Share capital NOK 200,000

NAGLESTAD BRUK EIENDOM AS is registered as a limited company in Lyngdal, Agder with organisation number 927436027. The business is classified under rental and operating of own or leased real estate (NACE 68.200). The company was incorporated in 2021. Registered share capital is NOK 200,000, divided into 100 shares. The company's stated purpose is: “Eie og leie ut fast eiendom, samt det som naturlig står i forbindelse med dette.”. The most recent filed accounts, for the 2025 financial year, show NOK 1.7m in revenue and NOK 848,000 in operating profit.

Key figures · 2025

Revenue
NOK 1.7m
Operating profit
NOK 848,000
Equity
NOK 3.9m
Est. value
NOK 4.6m

Financial health · 2025

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

Who owns NAGLESTAD BRUK EIENDOM AS?

KÅRE NAGLESTAD AS
NAGLESTAD BRUK EIENDOM AS
NOK 1.7m rev. · NOK 848,000 profit

NAGLESTAD BRUK EIENDOM AS has 2 registered shareholders:

All shareholders and roles →

Frequently asked questions about NAGLESTAD BRUK EIENDOM AS

Who owns NAGLESTAD BRUK EIENDOM AS?

KÅRE NAGLESTAD AS is the largest registered owner, with 50.0%.

What is the revenue of NAGLESTAD BRUK EIENDOM AS?

NAGLESTAD BRUK EIENDOM AS had revenue of NOK 1.7m in 2025.

Who is the general manager of NAGLESTAD BRUK EIENDOM AS?

Lyder Naglestad is registered as general manager of NAGLESTAD BRUK EIENDOM AS.

Where is NAGLESTAD BRUK EIENDOM AS based?

NAGLESTAD BRUK EIENDOM 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.