BIZTRAC BETA
Construction of residential and non-residential buildings

RAYMOND HELGESEN AS

Org. no. 916223927 Limited company (AS) Øksnes Incorporated 2015 Active
Ownership graph ↗
Revenue 2025 NOK 1.1m
Operating profit NOK −8,000
Equity NOK 868,000
Incorporated 2015
Share capital NOK 30,000

Signals

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

RAYMOND HELGESEN AS is registered as a limited company in Øksnes, Nordland with organisation number 916223927. The business is classified under construction of residential and non-residential buildings (NACE 41.000). The company was incorporated in 2015. Registered share capital is NOK 30,000, divided into 30 shares. The company's stated purpose is: “Snekkering, oppføring og vedlikehold av bygninger, herunder deltakelse i andre selskaper.”. The most recent filed accounts, for the 2025 financial year, show NOK 1.1m in revenue and NOK −8,000 in operating profit.

Key figures · 2025

Revenue
NOK 1.1m
Operating profit
NOK −8,000
Equity
NOK 868,000
Est. value
NOK 617,000

Financial health · 2025

Liquidity
2.08
Very good
Current assets ÷ current liabilities
Profitability
Not available
Return on total assets
Solidity
53.1%
Very good
Equity as a share of total capital

Who owns RAYMOND HELGESEN AS?

RAYMOND HELGESEN
RAYMOND HELGESEN AS
NOK 1.1m rev. · NOK −8,000 profit

RAYMOND HELGESEN AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about RAYMOND HELGESEN AS

Who owns RAYMOND HELGESEN AS?

RAYMOND HELGESEN is the largest registered owner, with 100.0%.

What is the revenue of RAYMOND HELGESEN AS?

RAYMOND HELGESEN AS had revenue of NOK 1.1m in 2025.

Who is the general manager of RAYMOND HELGESEN AS?

Raymond Helgesen is registered as general manager of RAYMOND HELGESEN AS.

Where is RAYMOND HELGESEN AS based?

RAYMOND HELGESEN AS has its business address in Myre.

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.