BIZTRAC BETA
Roofing activities

LIE BLIKK AS

Org. no. 988976849 Limited company (AS) Klepp Incorporated 2005 Active
Ownership graph ↗
Revenue 2025 NOK 185.8m
Operating profit NOK 10.2m
Equity NOK 24.3m
Incorporated 2005
Employees 102
Share capital NOK 100,000

Signals

1 flags
  • Ingen revisor Selskapet har ingen registrert revisor. Vanlig for små AS som har valgt bort revisjon, men verdt å merke seg.

LIE BLIKK AS is registered as a limited company in Klepp, Rogaland with organisation number 988976849. The business is classified under roofing activities (NACE 43.410). The company was incorporated in 2005 and has 102 registered employees. Registered share capital is NOK 100,000, divided into 1000 shares. The company's stated purpose is: “Produksjon av blikkenslagermateriell og utføring av blikkenslagerarbeid, herunder kjøp og salg av tilknyttede varer og utstyr.”. The most recent filed accounts, for the 2025 financial year, show NOK 185.8m in revenue and NOK 10.2m in operating profit.

Key figures · 2025

Revenue
NOK 185.8m
Operating profit
NOK 10.2m
Equity
NOK 24.3m
Est. value
NOK 45.2m

Financial health · 2025

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

Who owns LIE BLIKK AS?

LIE GRUPPEN AS
LIE BLIKK AS
NOK 185.8m rev. · NOK 10.2m profit

LIE BLIKK AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about LIE BLIKK AS

Who owns LIE BLIKK AS?

LIE GRUPPEN AS is the largest registered owner, with 100.0%.

What is the revenue of LIE BLIKK AS?

LIE BLIKK AS had revenue of NOK 185.8m in 2025.

Who is the general manager of LIE BLIKK AS?

Kate Mariann Lie is registered as general manager of LIE BLIKK AS.

Where is LIE BLIKK AS based?

LIE BLIKK AS has its business address in Klepp Stasjon.

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.