BIZTRAC BETA
COMPANY REGISTER PROFILE
975759458 ORG. NO. 2025 ACCOUNTS 8 SECTIONS
Active UPDATED 02.09.2026
Activities of sports clubs

LAVANGEN IDRETTSFORENING

Org. no. 975759458 Association/club/organisation (FLI) Lavangen Incorporated 1959 Active
Ownership graph ↗
Revenue 2025 NOK 589,000
Operating profit NOK 33,000
Equity NOK 2.0m
Incorporated 1959

LAVANGEN IDRETTSFORENING is registered as a association/club/organisation in Lavangen, Troms with organisation number 975759458. The business is classified under activities of sports clubs (NACE 93.120). The company was incorporated in 1959. The most recent filed accounts, for the 2025 financial year, show NOK 589,000 in revenue and NOK 33,000 in operating profit.

Key figures · 2025

Revenue
NOK 589,000
Operating profit
NOK 33,000
Equity
NOK 2.0m
Est. value
NOK 1.2m

Financial health · 2025

Liquidity
0.78
Weak
Current assets ÷ current liabilities
Profitability
Not available
Return on total assets
Solidity
53.8%
Very good
Equity as a share of total capital

Who owns LAVANGEN IDRETTSFORENING?

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

Frequently asked questions about LAVANGEN IDRETTSFORENING

What is the revenue of LAVANGEN IDRETTSFORENING?

LAVANGEN IDRETTSFORENING had revenue of NOK 589,000 in 2025.

Where is LAVANGEN IDRETTSFORENING based?

LAVANGEN IDRETTSFORENING has its business address in Tennevoll.

Property

Business address Skavmodalveien 103, 9357 Tennevoll
Cadastral unit 5518-68/318/0/0
Building Annen idrettsbygning · 1 unit

The address this company is registered at, from the company register and matched against the cadastre. It does not say who owns the property — a company may be a tenant, and the address is often its accountant's. Source: Brønnøysundregistrene and © Kartverket.

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

Report a problem

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