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

FISKERNES HUS AS

Org. no. 930861529 Limited company (AS) Ålesund Incorporated 1962 Active
Ownership graph ↗
Revenue 2025 NOK 1.1m
Operating profit NOK −98,000
Equity NOK 7.8m
Incorporated 1962
Share capital NOK 820,000

Signals

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

FISKERNES HUS AS is registered as a limited company in Ålesund, Møre og Romsdal with organisation number 930861529. The business is classified under rental and operating of own or leased real estate (NACE 68.200). The company was incorporated in 1962. Registered share capital is NOK 820,000, divided into 820 shares. The company's stated purpose is: “Kjøp, salg og utleie av fast eiendom, medvirke i andre selskaper innen samme virksomhet, samt alt som hører naturlig til dette.”. The most recent filed accounts, for the 2025 financial year, show NOK 1.1m in revenue and NOK −98,000 in operating profit.

Key figures · 2025

Revenue
NOK 1.1m
▲ +21 %
Operating profit
NOK −98,000
▲ +69 %
Equity
NOK 7.8m
▼ −1 %
Est. value
NOK 6.9m

Financial health · 2025

Liquidity
2.30
Very good
Current assets ÷ current liabilities
Profitability
-1.1%
Not satisfactory
Return on total assets
Solidity
91.6%
Very good
Equity as a share of total capital

Who owns FISKERNES HUS AS?

FISKERNES HUS AS
NOK 1.1m rev. · NOK −98,000 profit

FISKERNES HUS AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about FISKERNES HUS AS

Who owns FISKERNES HUS AS?

INCREMENTUM EIENDOM AS is the largest registered owner, with 100.0%.

What is the revenue of FISKERNES HUS AS?

FISKERNES HUS AS had revenue of NOK 1.1m in 2025.

Where is FISKERNES HUS AS based?

FISKERNES HUS AS has its business address in Ålesund.

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.