biztrac. BETA
COMPANY REGISTER PROFILE
824557772 ORG. NO. 2025 ACCOUNTS 8 SECTIONS
Active UPDATED 03.10.2026
Sports and recreation education

FANA PT- OG BEHANDLINGSSENTER AS

Org. no. 824557772 Limited company (AS) Bergen Incorporated 2020 Active
Ownership graph ↗
Revenue 2025 NOK 1.4m
Operating profit NOK 120,000
Equity NOK 684,000
Incorporated 2020
Share capital NOK 200,000

FANA PT- OG BEHANDLINGSSENTER AS is registered as a limited company in Bergen, Vestland with organisation number 824557772. The business is classified under sports and recreation education (NACE 85.510). The company was incorporated in 2020. Registered share capital is NOK 200,000, divided into 200000 shares. The company's stated purpose is: “Personlig trening, undervisning, utleie av fast eiendom.”. The most recent filed accounts, for the 2025 financial year, show NOK 1.4m in revenue and NOK 120,000 in operating profit.

Key figures · 2025

Revenue
NOK 1.4m
▼ −25 %
Operating profit
NOK 120,000
▲ +48 %
Equity
NOK 684,000
▲ +19 %
Est. value
NOK 996,000

Financial health · 2025

Liquidity
2.26
Very good
Current assets ÷ current liabilities
Profitability
13.1%
Good
Return on total assets
Solidity
56.8%
Very good
Equity as a share of total capital

Who owns FANA PT- OG BEHANDLINGSSENTER AS?

FANA PT- OG BEHANDLINGSSENTER AS
NOK 1.4m rev. · NOK 120,000 profit

FANA PT- OG BEHANDLINGSSENTER AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about FANA PT- OG BEHANDLINGSSENTER AS

Who owns FANA PT- OG BEHANDLINGSSENTER AS?

Chris-Andre Hummelsund Bernardino is the largest registered owner, with 100.0%.

What is the revenue of FANA PT- OG BEHANDLINGSSENTER AS?

FANA PT- OG BEHANDLINGSSENTER AS had revenue of NOK 1.4m in 2025.

Where is FANA PT- OG BEHANDLINGSSENTER AS based?

FANA PT- OG BEHANDLINGSSENTER AS has its business address in Eidsvåg I Åsane.

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

Report a problem

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