BIZTRAC BETA
Floor and wall covering

FLISELEGGER AS

Org. no. 991671781 Limited company (AS) Time Incorporated 2007 Active
Ownership graph ↗
Revenue 2024 NOK 4.5m
Operating profit NOK 341,000
Equity NOK 334,000
Incorporated 2007
Employees 5
Share capital NOK 100,000

FLISELEGGER AS is registered as a limited company in Time, Rogaland with organisation number 991671781. The business is classified under floor and wall covering (NACE 43.330). The company was incorporated in 2007 and has 5 registered employees. Registered share capital is NOK 100,000, divided into 100 shares. The company's stated purpose is: “Omsetning og legging av fliser og liknende, herunder å delta i andre virksomheter med liknende formål gjennom aksjetegning eller på annen måte.”. The most recent filed accounts, for the 2024 financial year, show NOK 4.5m in revenue and NOK 341,000 in operating profit.

Key figures · 2024

Revenue
NOK 4.5m
Operating profit
NOK 341,000
Equity
NOK 334,000
Est. value
NOK 1.2m

Financial health · 2025

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

Who owns FLISELEGGER AS?

SVEIN INGE LANDE
FLISELEGGER AS
NOK 4.5m rev. · NOK 341,000 profit

FLISELEGGER AS has 1 registered shareholder:

All shareholders and roles →

Which companies does FLISELEGGER AS own?

FLISELEGGER AS holds a stake in 1 company:

See the full ownership structure →

Frequently asked questions about FLISELEGGER AS

Who owns FLISELEGGER AS?

SVEIN INGE LANDE is the largest registered owner, with 100.0%.

What is the revenue of FLISELEGGER AS?

FLISELEGGER AS had revenue of NOK 4.5m in 2024.

Who is the general manager of FLISELEGGER AS?

Svein Inge Lande is registered as general manager of FLISELEGGER AS.

Where is FLISELEGGER AS based?

FLISELEGGER AS has its business address in Bryne.

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.