biztrac. BETA
COMPANY REGISTER PROFILE
917604835 ORG. NO. 2025 ACCOUNTS 7 SECTIONS
Active UPDATED 03.10.2026
Activities of housing cooperatives

MARISTOVA HOTELL-OG FRITIDSBOLIG EIERSEKSJONSSAMEIE

Org. no. 917604835 Condominium flat owner (ESEK) Alver Incorporated 2009 Active
Revenue 2025 NOK 390,000
Operating profit NOK −130,000
Equity NOK 125,000
Incorporated 2009

Signals

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

MARISTOVA HOTELL-OG FRITIDSBOLIG EIERSEKSJONSSAMEIE is registered as a condominium flat owner in Alver, Vestland with organisation number 917604835. The business is classified under activities of housing cooperatives (NACE 97.001). The company was incorporated in 2009. The company's stated purpose is: “Eierseksjonssameie”. The most recent filed accounts, for the 2025 financial year, show NOK 390,000 in revenue and NOK −130,000 in operating profit.

Key figures · 2025

Revenue
NOK 390,000
▲ +16 %
Operating profit
NOK −130,000
▲ +71 %
Equity
NOK 125,000
▼ −49 %
Est. value
NOK 276,000

Financial health · 2025

Liquidity
1.85
Good
Current assets ÷ current liabilities
Profitability
–
Not available
Return on total assets
Solidity
28.4%
Good
Equity as a share of total capital

Who owns MARISTOVA HOTELL-OG FRITIDSBOLIG EIERSEKSJONSSAMEIE?

No shareholders are registered for MARISTOVA HOTELL-OG FRITIDSBOLIG EIERSEKSJONSSAMEIE in open Norwegian sources. Shareholder data exists mainly for limited companies (AS/ASA).

Frequently asked questions about MARISTOVA HOTELL-OG FRITIDSBOLIG EIERSEKSJONSSAMEIE

What is the revenue of MARISTOVA HOTELL-OG FRITIDSBOLIG EIERSEKSJONSSAMEIE?

MARISTOVA HOTELL-OG FRITIDSBOLIG EIERSEKSJONSSAMEIE had revenue of NOK 390,000 in 2025.

Where is MARISTOVA HOTELL-OG FRITIDSBOLIG EIERSEKSJONSSAMEIE based?

MARISTOVA HOTELL-OG FRITIDSBOLIG EIERSEKSJONSSAMEIE has its business address in Alversund.

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.