BIZTRAC BETA
Sports and recreation education

BREAKING MARATHON LIMITS AS

Org. no. 923843744 Limited company (AS) Oslo Incorporated 2019 Active
Ownership graph ↗
Revenue 2024 NOK 4.8m
Operating profit NOK 469,000
Equity NOK 548,000
Incorporated 2019
Share capital NOK 30,000

Signals

1 flags
  • Nylig endring 2026-07-07 Adresseendring registrert 2026-07-07.

BREAKING MARATHON LIMITS AS is registered as a limited company in Oslo, Oslo with organisation number 923843744. The business is classified under sports and recreation education (NACE 85.510). The company was incorporated in 2019. Registered share capital is NOK 30,000, divided into 100 shares. The company's stated purpose is: “Undervisning innen idrett og rekreasjon.”. The most recent filed accounts, for the 2024 financial year, show NOK 4.8m in revenue and NOK 469,000 in operating profit.

Key figures · 2024

Revenue
NOK 4.8m
Operating profit
NOK 469,000
Equity
NOK 548,000
Est. value
NOK 2.5m

Financial health · 2024

Liquidity
1.93
Good
Current assets ÷ current liabilities
Profitability
Not available
Return on total assets
Solidity
65.7%
Very good
Equity as a share of total capital

Who owns BREAKING MARATHON LIMITS AS?

ANDREAS GRØGAARD
BREAKING MARATHON LIMITS AS
NOK 4.8m rev. · NOK 469,000 profit

BREAKING MARATHON LIMITS AS has 3 registered shareholders:

All shareholders and roles →

Frequently asked questions about BREAKING MARATHON LIMITS AS

Who owns BREAKING MARATHON LIMITS AS?

ANDREAS GRØGAARD is the largest registered owner, with 34.0%.

What is the revenue of BREAKING MARATHON LIMITS AS?

BREAKING MARATHON LIMITS AS had revenue of NOK 4.8m in 2024.

Who is the general manager of BREAKING MARATHON LIMITS AS?

Kristian Ulriksen is registered as general manager of BREAKING MARATHON LIMITS AS.

Where is BREAKING MARATHON LIMITS AS based?

BREAKING MARATHON LIMITS 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.