BIZTRAC BETA
Masonry and bricklaying activities

FLISELEGGEREN AS

Org. no. 998754496 Limited company (AS) Lindesnes Incorporated 2012 Active
Ownership graph ↗
Revenue 2025 NOK 281,000
Operating profit NOK −42,000
Equity NOK 142,000
Incorporated 2012
Share capital NOK 30,000

Signals

1 flags
  • Driftsunderskudd 2025 Siste driftsresultat er negativt (−42k kr).

FLISELEGGEREN AS is registered as a limited company in Lindesnes, Agder with organisation number 998754496. The business is classified under masonry and bricklaying activities (NACE 43.910). The company was incorporated in 2012. Registered share capital is NOK 30,000, divided into 100 shares. The company's stated purpose is: “Utføre/selge tjenester og produkter innenfor mur-, flis- og betongarbeid, og alt som naturlig hører inn under disse områder. ”. The most recent filed accounts, for the 2025 financial year, show NOK 281,000 in revenue and NOK −42,000 in operating profit.

Key figures · 2025

Revenue
NOK 281,000
Operating profit
NOK −42,000
Equity
NOK 142,000
Est. value
NOK 144,000

Financial health · 2025

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

Who owns FLISELEGGEREN AS?

ANNE KAREN ØVERLAND
FLISELEGGEREN AS
NOK 281,000 rev. · NOK −42,000 profit

FLISELEGGEREN AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about FLISELEGGEREN AS

Who owns FLISELEGGEREN AS?

ANNE KAREN ØVERLAND is the largest registered owner, with 100.0%.

What is the revenue of FLISELEGGEREN AS?

FLISELEGGEREN AS had revenue of NOK 281,000 in 2025.

Who is the general manager of FLISELEGGEREN AS?

Anne Karen Øverland is registered as general manager of FLISELEGGEREN AS.

Where is FLISELEGGEREN AS based?

FLISELEGGEREN AS has its business address in Mandal.

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.