BIZTRAC BETA
Manufacture of other builders' carpentry and joinery

LAFTEKLEDNING AS

Org. no. 988143790 Limited company (AS) Verdal Incorporated 2005 Active
Ownership graph ↗
Revenue 2024 NOK 963,000
Operating profit NOK −1.1m
Equity NOK −105,000
Incorporated 2005
Share capital NOK 138,000

Signals

2 flags
  • Negativ egenkapital 2024 Bokført egenkapital er negativ (−105k kr).
  • Driftsunderskudd 2024 Siste driftsresultat er negativt (−1,1 mill kr).

LAFTEKLEDNING AS is registered as a limited company in Verdal, Trøndelag with organisation number 988143790. The business is classified under manufacture of other builders' carpentry and joinery (NACE 16.230). The company was incorporated in 2005. Registered share capital is NOK 138,000, divided into 138 shares. The company's stated purpose is: “Produksjon av kledning og paneler til hytter og hus, oppsetting og salg av hytter, og alt som er naturlig forbundet hermed.”. The most recent filed accounts, for the 2024 financial year, show NOK 963,000 in revenue and NOK −1.1m in operating profit.

Key figures · 2024

Revenue
NOK 963,000
Operating profit
NOK −1.1m
Equity
NOK −105,000

Financial health · 2024

Liquidity
1.16
Satisfactory
Current assets ÷ current liabilities
Profitability
Not available
Return on total assets
Solidity
-6.7%
Weak
Equity as a share of total capital

Solidity capped at Weak because equity is below NOK 100,000.

Who owns LAFTEKLEDNING AS?

ODIN GRANHEIM AS
LAFTEKLEDNING AS
NOK 963,000 rev. · NOK −1.1m profit

LAFTEKLEDNING AS has 3 registered shareholders:

All shareholders and roles →

Frequently asked questions about LAFTEKLEDNING AS

Who owns LAFTEKLEDNING AS?

ODIN GRANHEIM AS is the largest registered owner, with 33.3%.

What is the revenue of LAFTEKLEDNING AS?

LAFTEKLEDNING AS had revenue of NOK 963,000 in 2024.

Where is LAFTEKLEDNING AS based?

LAFTEKLEDNING AS has its business address in Verdal.

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.