BIZTRAC BETA
COMPANY REGISTER PROFILE
912438309 ORG. NO. 2023 ACCOUNTS 7 SECTIONS
Active UPDATED 02.09.2026
Cultural history museum activities

AKERSELVA TREBÅTFORENING

Org. no. 912438309 Association/club/organisation (FLI) Oslo Incorporated 2013 Active
Ownership graph ↗
Revenue 2023 NOK 693,000
Operating profit NOK 1.6m
Equity NOK 219,000
Incorporated 2013

AKERSELVA TREBÅTFORENING is registered as a association/club/organisation in Oslo, Oslo with organisation number 912438309. The business is classified under cultural history museum activities (NACE 91.212). The company was incorporated in 2013. The most recent filed accounts, for the 2023 financial year, show NOK 693,000 in revenue and NOK 1.6m in operating profit.

Key figures · 2023

Revenue
NOK 693,000
Operating profit
NOK 1.6m
Equity
NOK 219,000
Est. value
NOK 4.7m

Financial health · 2023

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

Who owns AKERSELVA TREBÅTFORENING?

No shareholders are registered for AKERSELVA TREBÅTFORENING in open Norwegian sources. Shareholder data exists mainly for limited companies (AS/ASA).

Frequently asked questions about AKERSELVA TREBÅTFORENING

What is the revenue of AKERSELVA TREBÅTFORENING?

AKERSELVA TREBÅTFORENING had revenue of NOK 693,000 in 2023.

Where is AKERSELVA TREBÅTFORENING based?

AKERSELVA TREBÅTFORENING has its business address in Oslo.

Property

Business address Maridalsveien 3, 0178 Oslo
Cadastral unit 301-208/395/0/0

42 companies are registered at this address.

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.