biztrac. BETA
COMPANY REGISTER PROFILE
911914263 ORG. NO. 2025 ACCOUNTS 8 SECTIONS
Active UPDATED 03.10.2026
Activities of fitness centres

BRITO HOLDING AS

Org. no. 911914263 Limited company (AS) Osterøy Incorporated 2013 Active
Ownership graph ↗
Operating profit NOK −161,000
Equity NOK 3.5m
Incorporated 2013
Share capital NOK 30,000

Signals

1 flags
  • Driftsunderskudd 2025 Siste driftsresultat er negativt (−161k kr).

BRITO HOLDING AS is registered as a limited company in Osterøy, Vestland with organisation number 911914263. The business is classified under activities of fitness centres (NACE 93.130). The company was incorporated in 2013. Registered share capital is NOK 30,000, divided into 1000 shares. The company's stated purpose is: “Investere i andre aksjeselskaper og driftselskaper. Eie og forvalte aksjer og andeler i selskaper, virksomheter samt eiendommer. Finansiering av andre selskaper, virksomheter samt eiendommer.”.

Key figures · 2025

Operating profit
NOK −161,000
▲ +3 %
Equity
NOK 3.5m
▼ −18 %
Est. value
NOK 4.3m

Financial health · 2025

Liquidity
0.50
Not satisfactory
Current assets ÷ current liabilities
Profitability
-4.0%
Not satisfactory
Return on total assets
Solidity
98.5%
Very good
Equity as a share of total capital

Who owns BRITO HOLDING AS?

BRITO HOLDING AS
· NOK −161,000 profit

BRITO HOLDING AS has 1 registered shareholder:

All shareholders and roles →

Which companies does BRITO HOLDING AS own?

BRITO HOLDING AS holds stakes in 2 companies:

See the full ownership structure →

Frequently asked questions about BRITO HOLDING AS

Who owns BRITO HOLDING AS?

Jorge Quitral Brito is the largest registered owner, with 100.0%.

Who is the general manager of BRITO HOLDING AS?

Jorge Quitral Brito is registered as general manager of BRITO HOLDING AS.

Where is BRITO HOLDING AS based?

BRITO HOLDING AS has its business address in Valestrandsfossen.

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.