biztrac. BETA
COMPANY REGISTER PROFILE
939745084 ORG. NO. 2025 ACCOUNTS 7 SECTIONS
Active UPDATED 03.10.2026
Logging

LEKSVIK BYGDEALLMENNING

Org. no. 939745084 Association/club/organisation (FLI) Indre Fosen Incorporated 1990 Active
Ownership graph ↗
Revenue 2025 NOK 1.1m
Operating profit NOK −491,000
Equity NOK 4.2m
Incorporated 1990

Signals

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

LEKSVIK BYGDEALLMENNING is registered as a association/club/organisation in Indre Fosen, Trøndelag with organisation number 939745084. The business is classified under logging (NACE 02.200). The company was incorporated in 1990. The company's stated purpose is: “Skogsdrift: (salg av tømmer fra egen skog) Utmark: (utleie av elgvald, salg av jakt- og fiskekort,) (utleie av tomtefester for fritids- hus.)”. The most recent filed accounts, for the 2025 financial year, show NOK 1.1m in revenue and NOK −491,000 in operating profit.

Key figures · 2025

Revenue
NOK 1.1m
▲ +27 %
Operating profit
NOK −491,000
▼ −37 %
Equity
NOK 4.2m
▼ −9 %
Est. value
NOK 2.6m

Financial health · 2025

Liquidity
12.23
Very good
Current assets ÷ current liabilities
Profitability
-7.9%
Not satisfactory
Return on total assets
Solidity
91.9%
Very good
Equity as a share of total capital

Who owns LEKSVIK BYGDEALLMENNING?

No shareholders are registered for LEKSVIK BYGDEALLMENNING in open Norwegian sources. Shareholder data exists mainly for limited companies (AS/ASA).

Frequently asked questions about LEKSVIK BYGDEALLMENNING

What is the revenue of LEKSVIK BYGDEALLMENNING?

LEKSVIK BYGDEALLMENNING had revenue of NOK 1.1m in 2025.

Who is the general manager of LEKSVIK BYGDEALLMENNING?

Bjørn Ingolf Bakkhaug is registered as general manager of LEKSVIK BYGDEALLMENNING.

Where is LEKSVIK BYGDEALLMENNING based?

LEKSVIK BYGDEALLMENNING has its business address in Leksvik.

Source: Biztrac.no · Data from the Brønnøysund Register Centre and the Norwegian Tax Administration · Last updated 03.10.2026.

Report a problem

Found a technical fault, or something wrong in the data? Tell us what happened.