BIZTRAC BETA
All other professional, scientific and technical activities n.e.c.

HALLGREN & HALLGREN AS

Org. no. 964418659 Limited company (AS) Oslo Incorporated 1992 Active
Ownership graph ↗
Revenue 2024 NOK 1.4m
Operating profit NOK 145,000
Equity NOK −49,000
Incorporated 1992
Share capital NOK 100,000

Signals

1 flags
  • Negativ egenkapital 2024 Bokført egenkapital er negativ (−49k kr).

HALLGREN & HALLGREN AS is registered as a limited company in Oslo, Oslo with organisation number 964418659. The business is classified under all other professional, scientific and technical activities n.e.c. (NACE 74.990). The company was incorporated in 1992. Registered share capital is NOK 100,000, divided into 1000 shares. The company's stated purpose is: “Konsulentvirksomhet og rådgivning, generelt, men spesielt vedr eierskap, drift og forvaltning av eiendom”. The most recent filed accounts, for the 2024 financial year, show NOK 1.4m in revenue and NOK 145,000 in operating profit.

Key figures · 2024

Revenue
NOK 1.4m
Operating profit
NOK 145,000
Equity
NOK −49,000
Est. value
NOK 1.4m

Financial health · 2024

Liquidity
0.95
Weak
Current assets ÷ current liabilities
Profitability
Not available
Return on total assets
Solidity
-5.6%
Weak
Equity as a share of total capital

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

Who owns HALLGREN & HALLGREN AS?

KAI HALLGREN
HALLGREN & HALLGREN AS
NOK 1.4m rev. · NOK 145,000 profit

HALLGREN & HALLGREN AS has 2 registered shareholders:

All shareholders and roles →

Frequently asked questions about HALLGREN & HALLGREN AS

Who owns HALLGREN & HALLGREN AS?

KAI HALLGREN is the largest registered owner, with 50.0%.

What is the revenue of HALLGREN & HALLGREN AS?

HALLGREN & HALLGREN AS had revenue of NOK 1.4m in 2024.

Where is HALLGREN & HALLGREN AS based?

HALLGREN & HALLGREN AS has its business address in Oslo.

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.