BIZTRAC BETA
Beverage serving activities

TANKEN ARENA AS

Org. no. 935159636 Limited company (AS) Ål Incorporated 2025 Active
Ownership graph ↗
Revenue 2025 NOK 1.9m
Operating profit NOK 32,000
Equity NOK 49,000
Incorporated 2025
Share capital NOK 30,000

TANKEN ARENA AS is registered as a limited company in Ål, Buskerud with organisation number 935159636. The business is classified under beverage serving activities (NACE 56.300). The company was incorporated in 2025. Registered share capital is NOK 30,000, divided into 1000 shares. The company's stated purpose is: “Drift og utleie av eiendom, coworking-sted med tilhørende aktiviteter, servering, bar, drift av scene med konsertvirksomhet/foredrag/standup samt utleie av møterom, konferanselokaler, selskapslokaler og arrangementsutstyr.”. The most recent filed accounts, for the 2025 financial year, show NOK 1.9m in revenue and NOK 32,000 in operating profit.

Key figures · 2025

Revenue
NOK 1.9m
Operating profit
NOK 32,000
Equity
NOK 49,000
Est. value
NOK 134,000

Financial health · 2025

Liquidity
1.29
Satisfactory
Current assets ÷ current liabilities
Profitability
Not available
Return on total assets
Solidity
8.3%
Weak
Equity as a share of total capital

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

Who owns TANKEN ARENA AS?

MJØLKESPANNHOLDING AS
TANKEN ARENA AS
NOK 1.9m rev. · NOK 32,000 profit

TANKEN ARENA AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about TANKEN ARENA AS

Who owns TANKEN ARENA AS?

MJØLKESPANNHOLDING AS is the largest registered owner, with 100.0%.

What is the revenue of TANKEN ARENA AS?

TANKEN ARENA AS had revenue of NOK 1.9m in 2025.

Who is the general manager of TANKEN ARENA AS?

Magnus Tveito is registered as general manager of TANKEN ARENA AS.

Where is TANKEN ARENA AS based?

TANKEN ARENA AS has its business address in Ål.

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.