BIZTRAC BETA
Sports and recreation education

ATLET TRENING AS

Org. no. 913936159 Limited company (AS) Bergen Incorporated 2014 Active
Ownership graph ↗
Revenue 2025 NOK 0
Operating profit NOK 0
Equity NOK −769,000
Incorporated 2014
Share capital NOK 30,000

Signals

1 flags
  • Negativ egenkapital 2025 Bokført egenkapital er negativ (−769k kr).

ATLET TRENING AS is registered as a limited company in Bergen, Vestland with organisation number 913936159. The business is classified under sports and recreation education (NACE 85.510). The company was incorporated in 2014. Registered share capital is NOK 30,000, divided into 100 shares. The company's stated purpose is: “Drive med personlig trening, muskel- og massasjeterapi, deltakelse i andre selskaper, samt hva som står i forbindelse hermed.”. The most recent filed accounts, for the 2025 financial year, show NOK 0 in revenue and NOK 0 in operating profit.

Key figures · 2025

Revenue
NOK 0
Operating profit
NOK 0
Equity
NOK −769,000

Financial health · 2025

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

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

Who owns ATLET TRENING AS?

ANDERS MARTIN HANSEN
ATLET TRENING AS
NOK 0 rev. · NOK 0 profit

ATLET TRENING AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about ATLET TRENING AS

Who owns ATLET TRENING AS?

ANDERS MARTIN HANSEN is the largest registered owner, with 100.0%.

What is the revenue of ATLET TRENING AS?

ATLET TRENING AS had revenue of NOK 0 in 2025.

Who is the general manager of ATLET TRENING AS?

Anders Martin Hansen is registered as general manager of ATLET TRENING AS.

Where is ATLET TRENING AS based?

ATLET TRENING AS has its business address in Blomsterdalen.

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.