BIZTRAC BETA
Activities of fitness centres

MUDO TVEITA AS

Org. no. 898175022 Limited company (AS) Oslo Incorporated 2012 Active
Ownership graph ↗
Revenue 2025 NOK 2.0m
Operating profit NOK −368,000
Equity NOK −1.1m
Incorporated 2012
Share capital NOK 30,000

Signals

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

MUDO TVEITA AS is registered as a limited company in Oslo, Oslo with organisation number 898175022. The business is classified under activities of fitness centres (NACE 93.130). The company was incorporated in 2012. Registered share capital is NOK 30,000, divided into 300 shares. The company's stated purpose is: “Drift av treningssenter og investering i virksomhet relatert til dette.”. The most recent filed accounts, for the 2025 financial year, show NOK 2.0m in revenue and NOK −368,000 in operating profit.

Key figures · 2025

Revenue
NOK 2.0m
Operating profit
NOK −368,000
Equity
NOK −1.1m

Financial health · 2025

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

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

Who owns MUDO TVEITA AS?

GUNNAR TORE BRATLI
MUDO TVEITA AS
NOK 2.0m rev. · NOK −368,000 profit

MUDO TVEITA AS has 2 registered shareholders:

All shareholders and roles →

Frequently asked questions about MUDO TVEITA AS

Who owns MUDO TVEITA AS?

GUNNAR TORE BRATLI is the largest registered owner, with 90.5%.

What is the revenue of MUDO TVEITA AS?

MUDO TVEITA AS had revenue of NOK 2.0m in 2025.

Who is the general manager of MUDO TVEITA AS?

Gunnar Tore Bratli is registered as general manager of MUDO TVEITA AS.

Where is MUDO TVEITA AS based?

MUDO TVEITA AS has its business address in Oslo.

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.