BIZTRAC BETA
Joinery installation

LEKSVIK BYGG AS

Org. no. 912178943 Limited company (AS) Indre Fosen Incorporated 2013 Active
Ownership graph ↗
Revenue 2025 NOK 202,000
Operating profit NOK 119,000
Equity NOK −34,000
Incorporated 2013
Share capital NOK 30,000

Signals

1 flags
  • Negativ egenkapital 2025 Bokført egenkapital er negativ (−34k kr).

LEKSVIK BYGG AS is registered as a limited company in Indre Fosen, Trøndelag with organisation number 912178943. The business is classified under joinery installation (NACE 43.320). The company was incorporated in 2013. Registered share capital is NOK 30,000, divided into 30 shares. The company's stated purpose is: “Tømrerarbeid vedrørende nybygg og rehabilitering gamle bygg. Montering av butikkreoler og salg av ved.”. The most recent filed accounts, for the 2025 financial year, show NOK 202,000 in revenue and NOK 119,000 in operating profit.

Key figures · 2025

Revenue
NOK 202,000
Operating profit
NOK 119,000
Equity
NOK −34,000
Est. value
NOK 595,000

Financial health · 2025

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

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

Who owns LEKSVIK BYGG AS?

JAN VANGEN
LEKSVIK BYGG AS
NOK 202,000 rev. · NOK 119,000 profit

LEKSVIK BYGG AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about LEKSVIK BYGG AS

Who owns LEKSVIK BYGG AS?

JAN VANGEN is the largest registered owner, with 100.0%.

What is the revenue of LEKSVIK BYGG AS?

LEKSVIK BYGG AS had revenue of NOK 202,000 in 2025.

Who is the general manager of LEKSVIK BYGG AS?

Jan Vangen is registered as general manager of LEKSVIK BYGG AS.

Where is LEKSVIK BYGG AS based?

LEKSVIK BYGG AS has its business address in Leksvik.

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.