BIZTRAC BETA
Rental and operating of own or leased real estate

FISKE NÆRINGSEIENDOM AS

Org. no. 916544871 Limited company (AS) Molde Incorporated 2016 Active
Ownership graph ↗
Revenue 2025 NOK 333,000
Operating profit NOK 169,000
Equity NOK 465,000
Incorporated 2016
Share capital NOK 400,000

FISKE NÆRINGSEIENDOM AS is registered as a limited company in Molde, Møre og Romsdal with organisation number 916544871. The business is classified under rental and operating of own or leased real estate (NACE 68.200). The company was incorporated in 2016. Registered share capital is NOK 400,000, divided into 400 shares. The company's stated purpose is: “Eie, leie og forvalte fast eiendom samt alt som står i forbindelse med dette herunder å eie aksjer i andre selskap.”. The most recent filed accounts, for the 2025 financial year, show NOK 333,000 in revenue and NOK 169,000 in operating profit.

Key figures · 2025

Revenue
NOK 333,000
Operating profit
NOK 169,000
Equity
NOK 465,000
Est. value
NOK 540,000

Financial health · 2025

Liquidity
1.11
Satisfactory
Current assets ÷ current liabilities
Profitability
Not available
Return on total assets
Solidity
18.9%
Good
Equity as a share of total capital

Who owns FISKE NÆRINGSEIENDOM AS?

OVE FISKE
FISKE NÆRINGSEIENDOM AS
NOK 333,000 rev. · NOK 169,000 profit

FISKE NÆRINGSEIENDOM AS has 3 registered shareholders:

All shareholders and roles →

Frequently asked questions about FISKE NÆRINGSEIENDOM AS

Who owns FISKE NÆRINGSEIENDOM AS?

OVE FISKE is the largest registered owner, with 65.0%.

What is the revenue of FISKE NÆRINGSEIENDOM AS?

FISKE NÆRINGSEIENDOM AS had revenue of NOK 333,000 in 2025.

Who is the general manager of FISKE NÆRINGSEIENDOM AS?

Ove Fiske is registered as general manager of FISKE NÆRINGSEIENDOM AS.

Where is FISKE NÆRINGSEIENDOM AS based?

FISKE NÆRINGSEIENDOM AS has its business address in Molde.

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.