BIZTRAC BETA
COMPANY REGISTER PROFILE
938512299 ORG. NO. 2025 ACCOUNTS 7 SECTIONS
Active UPDATED 02.09.2026
Accounting and bookkeeping

HELLESYLT REKNESKAP AS

Org. no. 938512299 Limited company (AS) Stranda Incorporated 1985 Active
Ownership graph ↗
Revenue 2025 NOK 2.5m
Operating profit NOK 360,000
Equity NOK 1.5m
Incorporated 1985
Share capital NOK 100,000

HELLESYLT REKNESKAP AS is registered as a limited company in Stranda, Møre og Romsdal with organisation number 938512299. The business is classified under accounting and bookkeeping (NACE 69.202). The company was incorporated in 1985. Registered share capital is NOK 100,000, divided into 100 shares. The company's stated purpose is: “Drive regnskapsførsel, økonomisk rådgivning og det som måtte stå i forbindelse med dette.”. The most recent filed accounts, for the 2025 financial year, show NOK 2.5m in revenue and NOK 360,000 in operating profit.

Key figures · 2025

Revenue
NOK 2.5m
▲ +3 %
Operating profit
NOK 360,000
▲ +22 %
Equity
NOK 1.5m
▲ +13 %
Est. value
NOK 2.7m

Financial health · 2025

Liquidity
2.60
Very good
Current assets ÷ current liabilities
Profitability
19.7%
Very good
Return on total assets
Solidity
71.0%
Very good
Equity as a share of total capital

Who owns HELLESYLT REKNESKAP AS?

HELLESYLT REKNESKAP AS
NOK 2.5m rev. · NOK 360,000 profit

HELLESYLT REKNESKAP AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about HELLESYLT REKNESKAP AS

Who owns HELLESYLT REKNESKAP AS?

ARILD HOLE is the largest registered owner, with 100.0%.

What is the revenue of HELLESYLT REKNESKAP AS?

HELLESYLT REKNESKAP AS had revenue of NOK 2.5m in 2025.

Who is the general manager of HELLESYLT REKNESKAP AS?

Arild Hole is registered as general manager of HELLESYLT REKNESKAP AS.

Where is HELLESYLT REKNESKAP AS based?

HELLESYLT REKNESKAP AS has its business address in Hellesylt.

Source: Biztrac.no · Data from the Brønnøysund Register Centre and the Norwegian Tax Administration · Last updated 02.09.2026.

Report a problem

Found a technical fault, or something wrong in the data? Tell us what happened.