BIZTRAC BETA
COMPANY REGISTER PROFILE
820224892 ORG. NO. 2025 ACCOUNTS 7 SECTIONS
Active UPDATED 02.09.2026
Day spa, sauna and steam bath activities

ATLETICO NESHALLEN AS

Org. no. 820224892 Limited company (AS) Nes Incorporated 2017 Active
Ownership graph ↗
Revenue 2025 NOK 2.3m
Operating profit NOK 24,000
Equity NOK 128,000
Incorporated 2017
Share capital NOK 40,000

ATLETICO NESHALLEN AS is registered as a limited company in Nes, Akershus with organisation number 820224892. The business is classified under day spa, sauna and steam bath activities (NACE 96.230). The company was incorporated in 2017. Registered share capital is NOK 40,000, divided into 1000 shares. The company's stated purpose is: “Treningssenter og annet som naturlig faller sammen med dette.”. The most recent filed accounts, for the 2025 financial year, show NOK 2.3m in revenue and NOK 24,000 in operating profit.

Key figures · 2025

Revenue
NOK 2.3m
▼ −3 %
Operating profit
NOK 24,000
▼ −89 %
Equity
NOK 128,000
▲ +20 %
Est. value
NOK 328,000

Financial health · 2025

Liquidity
0.90
Weak
Current assets ÷ current liabilities
Profitability
6.6%
Satisfactory
Return on total assets
Solidity
41.3%
Very good
Equity as a share of total capital

Who owns ATLETICO NESHALLEN AS?

ATLETICO NESHALLEN AS
NOK 2.3m rev. · NOK 24,000 profit

ATLETICO NESHALLEN AS has 2 registered shareholders:

All shareholders and roles →

Frequently asked questions about ATLETICO NESHALLEN AS

Who owns ATLETICO NESHALLEN AS?

TORE ANDRÉ HØGDA is the largest registered owner, with 50.0%.

What is the revenue of ATLETICO NESHALLEN AS?

ATLETICO NESHALLEN AS had revenue of NOK 2.3m in 2025.

Who is the general manager of ATLETICO NESHALLEN AS?

Henrik Alexander Bjerke is registered as general manager of ATLETICO NESHALLEN AS.

Where is ATLETICO NESHALLEN AS based?

ATLETICO NESHALLEN AS has its business address in Årnes.

Source: Biztrac.no · Data from the Brønnøysund Register Centre and the Norwegian Tax Administration · Last updated 02.09.2026.

Report a problem

Found a technical fault, or something wrong in the data? Tell us what happened.