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

UNITE PERFORMANCE LARVIK AS

Org. no. 914472954 Limited company (AS) Larvik Incorporated 2014 Active
Ownership graph ↗
Revenue 2025 NOK 1.4m
Operating profit NOK 2,000
Equity NOK 76,000
Incorporated 2014
Share capital NOK 110,000

UNITE PERFORMANCE LARVIK AS is registered as a limited company in Larvik, Vestfold with organisation number 914472954. The business is classified under activities of fitness centres (NACE 93.130). The company was incorporated in 2014. Registered share capital is NOK 110,000, divided into 100 shares. The company's stated purpose is: “Funksjonell trening og helse, og det som naturlig hører sammen med dette samt deltagelse i andre selskaper.”. The most recent filed accounts, for the 2025 financial year, show NOK 1.4m in revenue and NOK 2,000 in operating profit.

Former names: CROSSFIT LARVIK AS

Key figures · 2025

Revenue
NOK 1.4m
▼ −22 %
Operating profit
NOK 2,000
▲ +100 %
Equity
NOK 76,000
▲ +1 %
Est. value
NOK 40,000

Financial health · 2025

Liquidity
1.28
Satisfactory
Current assets ÷ current liabilities
Profitability
0.8%
Not satisfactory
Return on total assets
Solidity
51.9%
Weak
Equity as a share of total capital

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

Who owns UNITE PERFORMANCE LARVIK AS?

UNITE PERFORMANCE LARVIK AS
NOK 1.4m rev. · NOK 2,000 profit

UNITE PERFORMANCE LARVIK AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about UNITE PERFORMANCE LARVIK AS

Who owns UNITE PERFORMANCE LARVIK AS?

Ibrahim Hindawi is the largest registered owner, with 100.0%.

What is the revenue of UNITE PERFORMANCE LARVIK AS?

UNITE PERFORMANCE LARVIK AS had revenue of NOK 1.4m in 2025.

Where is UNITE PERFORMANCE LARVIK AS based?

UNITE PERFORMANCE LARVIK AS has its business address in Larvik.

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.