biztrac. BETA
COMPANY REGISTER PROFILE
986168087 ORG. NO. 2019 ACCOUNTS 8 SECTIONS
Active UPDATED 03.10.2026
Sports and recreation education

DANSEKLUBBEN STUDIO 1

Org. no. 986168087 Association/club/organisation (FLI) Lørenskog Incorporated 2002 Active
Ownership graph ↗
Revenue 2019 NOK 4.9m
Operating profit NOK −29,000
Equity NOK −1.0m
Incorporated 2002
Employees 27

Signals

2 flags
  • Negativ egenkapital 2019 Bokført egenkapital er negativ (−1,0 mill kr).
  • Driftsunderskudd 2019 Siste driftsresultat er negativt (−29k kr).

DANSEKLUBBEN STUDIO 1 is registered as a association/club/organisation in Lørenskog, Akershus with organisation number 986168087. The business is classified under sports and recreation education (NACE 85.510). The company was incorporated in 2002 and has 27 registered employees. The most recent filed accounts, for the 2019 financial year, show NOK 4.9m in revenue and NOK −29,000 in operating profit.

Key figures · 2019

Revenue
NOK 4.9m
▲ +18 %
Operating profit
NOK −29,000
▲ +94 %
Equity
NOK −1.0m
▼ −3 %

Financial health · 2019

Liquidity
0.30
Not satisfactory
Current assets ÷ current liabilities
Profitability
-5.7%
Not satisfactory
Return on total assets
Solidity
-205.8%
Weak
Equity as a share of total capital

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

Who owns DANSEKLUBBEN STUDIO 1?

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

Frequently asked questions about DANSEKLUBBEN STUDIO 1

What is the revenue of DANSEKLUBBEN STUDIO 1?

DANSEKLUBBEN STUDIO 1 had revenue of NOK 4.9m in 2019.

Who is the general manager of DANSEKLUBBEN STUDIO 1?

Ina Michelle Linnerud is registered as general manager of DANSEKLUBBEN STUDIO 1.

Where is DANSEKLUBBEN STUDIO 1 based?

DANSEKLUBBEN STUDIO 1 has its business address in Lørenskog.

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.