BIZTRAC BETA
Rental and operating of own or leased real estate

KONSMO FLERBRUKSHALL AS

Org. no. 993509159 Limited company (AS) Lyngdal Incorporated 2008 Active
Ownership graph ↗
Revenue 2025 NOK 931,000
Operating profit NOK 486,000
Equity NOK 234,000
Incorporated 2008
Share capital NOK 100,000

KONSMO FLERBRUKSHALL AS is registered as a limited company in Lyngdal, Agder with organisation number 993509159. The business is classified under rental and operating of own or leased real estate (NACE 68.200). The company was incorporated in 2008. Registered share capital is NOK 100,000, divided into 100 shares. The company's stated purpose is: “Kjøp, salg, drift og utleie av eiendom. Selskapet skal drives uten eget økonomisk formål.”. The most recent filed accounts, for the 2025 financial year, show NOK 931,000 in revenue and NOK 486,000 in operating profit.

Key figures · 2025

Revenue
NOK 931,000
Operating profit
NOK 486,000
Equity
NOK 234,000
Est. value
NOK 446,000

Financial health · 2024

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

Who owns KONSMO FLERBRUKSHALL AS?

KONSMO IDRETTSLAG
KONSMO FLERBRUKSHALL AS
NOK 931,000 rev. · NOK 486,000 profit

KONSMO FLERBRUKSHALL AS has 2 registered shareholders:

All shareholders and roles →

Frequently asked questions about KONSMO FLERBRUKSHALL AS

Who owns KONSMO FLERBRUKSHALL AS?

KONSMO IDRETTSLAG is the largest registered owner, with 51.0%.

What is the revenue of KONSMO FLERBRUKSHALL AS?

KONSMO FLERBRUKSHALL AS had revenue of NOK 931,000 in 2025.

Who is the general manager of KONSMO FLERBRUKSHALL AS?

Kjell Asbjørn Valand is registered as general manager of KONSMO FLERBRUKSHALL AS.

Where is KONSMO FLERBRUKSHALL AS based?

KONSMO FLERBRUKSHALL 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.