biztrac. BETA
COMPANY REGISTER PROFILE
997427831 ORG. NO. 2025 ACCOUNTS 7 SECTIONS
Active UPDATED 03.10.2026
Other real estate activities on a fee or contract basis

HELGESENSGATE 44 AS

Org. no. 997427831 Limited company (AS) Bærum Incorporated 2011 Active
Revenue 2025 NOK 2.0m
Operating profit NOK 1.7m
Equity NOK 5.0m
Incorporated 2011
Share capital NOK 100,000

Signals

1 flags
  • Ingen revisor Selskapet har ingen registrert revisor. Vanlig for små AS som har valgt bort revisjon, men verdt å merke seg.

HELGESENSGATE 44 AS is registered as a limited company in Bærum, Akershus with organisation number 997427831. The business is classified under other real estate activities on a fee or contract basis (NACE 68.320). The company was incorporated in 2011. Registered share capital is NOK 100,000, divided into 100 shares. The company's stated purpose is: “Eie og forvaltning av eiendom og alt som står i naturlig forbindelse med dette.”. The most recent filed accounts, for the 2025 financial year, show NOK 2.0m in revenue and NOK 1.7m in operating profit.

Key figures · 2025

Revenue
NOK 2.0m
▼ −2 %
Operating profit
NOK 1.7m
▼ −4 %
Equity
NOK 5.0m
▲ +16 %
Est. value
NOK 6.3m

Financial health · 2025

Liquidity
2.95
Very good
Current assets ÷ current liabilities
Profitability
11.2%
Good
Return on total assets
Solidity
33.1%
Good
Equity as a share of total capital

Who owns HELGESENSGATE 44 AS?

HELGESENSGATE 44 AS
NOK 2.0m rev. · NOK 1.7m profit

HELGESENSGATE 44 AS has 2 registered shareholders:

All shareholders and roles →

Frequently asked questions about HELGESENSGATE 44 AS

Who owns HELGESENSGATE 44 AS?

OK INVEST HOLDING AS is the largest registered owner, with 91.0%.

What is the revenue of HELGESENSGATE 44 AS?

HELGESENSGATE 44 AS had revenue of NOK 2.0m in 2025.

Where is HELGESENSGATE 44 AS based?

HELGESENSGATE 44 AS has its business address in Østerås.

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.