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

KOLL, IDRETTSLAGET

Org. no. 976710274 Association/club/organisation (FLI) Oslo Incorporated 1940 Active
Ownership graph ↗
Revenue 2025 NOK 11.1m
Operating profit NOK 973,000
Equity NOK 8.6m
Incorporated 1940
Employees 62

KOLL, IDRETTSLAGET is registered as a association/club/organisation in Oslo, Oslo with organisation number 976710274. The business is classified under activities of sports clubs (NACE 93.120). The company was incorporated in 1940 and has 62 registered employees. The most recent filed accounts, for the 2025 financial year, show NOK 11.1m in revenue and NOK 973,000 in operating profit.

Former names: IDRETTSLAGET KOLL

Key figures · 2025

Revenue
NOK 11.1m
Operating profit
NOK 973,000
Equity
NOK 8.6m
Est. value
NOK 9.5m

Financial health · 2025

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

Who owns KOLL, IDRETTSLAGET?

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

Frequently asked questions about KOLL, IDRETTSLAGET

What is the revenue of KOLL, IDRETTSLAGET?

KOLL, IDRETTSLAGET had revenue of NOK 11.1m in 2025.

Where is KOLL, IDRETTSLAGET based?

KOLL, IDRETTSLAGET has its business address in Oslo.

Property

Business address c/o Arne Nesset Tåsenveien 102D, 0880 Oslo
Cadastral unit 301-54/271/0/0
Building Tomannsbolig, vertikal · 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.