BIZTRAC BETA
COMPANY REGISTER PROFILE
934398513 ORG. NO. 2025 ACCOUNTS 7 SECTIONS
Active UPDATED 15.06.2026
Uoppgitt

GRUPPEN BALCAZAR AS

Org. no. 934398513 Limited company (AS) Bærum Incorporated 2024 Active
Ownership graph ↗
Revenue 2025 NOK 50,000
Operating profit NOK 527
Equity NOK 13,000
Incorporated 2024
Share capital NOK 30,000

GRUPPEN BALCAZAR AS is registered as a limited company in Bærum, Akershus with organisation number 934398513. The business is classified under uoppgitt (NACE 00.000). The company was incorporated in 2024. Registered share capital is NOK 30,000, divided into 30000 shares. The company's stated purpose is: “Investere i selskaper og eiendom og alt annet som naturlig faller sammen med dette, herunder å delta i andre selskaper med lignende virksomhet, kjøp og salg av aksjer, eller på annen måte gjøre seg interessert i andre foretagende.”. The most recent filed accounts, for the 2025 financial year, show NOK 50,000 in revenue and NOK 527 in operating profit.

Key figures · 2025

Revenue
NOK 50,000
Operating profit
NOK 527
Equity
NOK 13,000
Est. value
NOK 9,000

Financial health · 2025

Liquidity
1.26
Satisfactory
Current assets ÷ current liabilities
Profitability
Not available
Return on total assets
Solidity
20.9%
Weak
Equity as a share of total capital

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

Who owns GRUPPEN BALCAZAR AS?

RANDHY JOEL BALCAZAR EFFIO
GRUPPEN BALCAZAR AS
NOK 50,000 rev. · NOK 527 profit

GRUPPEN BALCAZAR AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about GRUPPEN BALCAZAR AS

Who owns GRUPPEN BALCAZAR AS?

RANDHY JOEL BALCAZAR EFFIO is the largest registered owner, with 100.0%.

What is the revenue of GRUPPEN BALCAZAR AS?

GRUPPEN BALCAZAR AS had revenue of NOK 50,000 in 2025.

Where is GRUPPEN BALCAZAR AS based?

GRUPPEN BALCAZAR AS has its business address in Lysaker.

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.