biztrac. BETA
COMPANY REGISTER PROFILE
931994840 ORG. NO. 2025 ACCOUNTS 8 SECTIONS
Active UPDATED 03.10.2026
Rental and operating of own or leased real estate

ROFISK BERGTUN AS

Org. no. 931994840 Limited company (AS) Ålesund Incorporated 2023 Active
Ownership graph ↗
Operating profit NOK −15,000
Equity NOK 2.6m
Incorporated 2023
Share capital NOK 263,000

Signals

3 flags
  • Driftsunderskudd 2025 Siste driftsresultat er negativt (−15k kr).
  • Ingen revisor Selskapet har ingen registrert revisor. Vanlig for små AS som har valgt bort revisjon, men verdt å merke seg.
  • Nylig endring 2026-09-17 Adresseendring registrert 2026-09-17.

ROFISK BERGTUN AS is registered as a limited company in Ålesund, Møre og Romsdal with organisation number 931994840. The business is classified under rental and operating of own or leased real estate (NACE 68.200). The company was incorporated in 2023. Registered share capital is NOK 263,000, divided into 25000 shares. The company's stated purpose is: “Eie og forvalte aksjer og andre selskapsandeler, samt tilhørende virksomhet.”.

Key figures · 2025

Operating profit
NOK −15,000
▼ −20 %
Equity
NOK 2.6m
▼ −1 %
Est. value
NOK 2.4m

Financial health · 2025

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

Who owns ROFISK BERGTUN AS?

ROFISK BERGTUN AS
· NOK −15,000 profit

ROFISK BERGTUN AS has 1 registered shareholder:

All shareholders and roles →

Which companies does ROFISK BERGTUN AS own?

ROFISK BERGTUN AS holds a stake in 1 company:

See the full ownership structure →

Frequently asked questions about ROFISK BERGTUN AS

Who owns ROFISK BERGTUN AS?

ROFISK AS is the largest registered owner, with 100.0%.

Where is ROFISK BERGTUN AS based?

ROFISK BERGTUN AS has its business address in Harøy.

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.