BIZTRAC BETA
Sports and recreation education

HOT BIKRAMYOGA AS

Org. no. 911553074 Limited company (AS) Bærum Incorporated 2013 Active
Ownership graph ↗
Revenue 2025 NOK 3.4m
Operating profit NOK 77,000
Equity NOK −1.7m
Incorporated 2013
Share capital NOK 30,000

Signals

1 flags
  • Negativ egenkapital 2025 Bokført egenkapital er negativ (−1,7 mill kr).

HOT BIKRAMYOGA AS is registered as a limited company in Bærum, Akershus with organisation number 911553074. The business is classified under sports and recreation education (NACE 85.510). The company was incorporated in 2013. Registered share capital is NOK 30,000, divided into 100 shares. The company's stated purpose is: “Salg av yogaundervisning inkludert yogautstyr og relaterte kostholdsprodukter.”. The most recent filed accounts, for the 2025 financial year, show NOK 3.4m in revenue and NOK 77,000 in operating profit.

Key figures · 2025

Revenue
NOK 3.4m
Operating profit
NOK 77,000
Equity
NOK −1.7m
Est. value
NOK 476,000

Financial health · 2025

Liquidity
0.36
Not satisfactory
Current assets ÷ current liabilities
Profitability
Not available
Return on total assets
Solidity
-80.7%
Weak
Equity as a share of total capital

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

Who owns HOT BIKRAMYOGA AS?

JOACHIM SKIBENES
HOT BIKRAMYOGA AS
NOK 3.4m rev. · NOK 77,000 profit

HOT BIKRAMYOGA AS has 2 registered shareholders:

All shareholders and roles →

Which companies does HOT BIKRAMYOGA AS own?

HOT BIKRAMYOGA AS holds a stake in 1 company:

See the full ownership structure →

Frequently asked questions about HOT BIKRAMYOGA AS

Who owns HOT BIKRAMYOGA AS?

JOACHIM SKIBENES is the largest registered owner, with 65.0%.

What is the revenue of HOT BIKRAMYOGA AS?

HOT BIKRAMYOGA AS had revenue of NOK 3.4m in 2025.

Where is HOT BIKRAMYOGA AS based?

HOT BIKRAMYOGA AS has its business address in Høvik.

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.