BIZTRAC BETA
Holiday and other short-stay accommodation

FURREHYTTER AS

Org. no. 928667413 Limited company (AS) Stavanger Incorporated 2022 Active
Ownership graph ↗
Revenue 2024 NOK 4.4m
Operating profit NOK −19,000
Equity NOK 10.1m
Incorporated 2022
Share capital NOK 2.0m

Signals

1 flags
  • Driftsunderskudd 2024 Siste driftsresultat er negativt (−19k kr).

FURREHYTTER AS is registered as a limited company in Stavanger, Rogaland with organisation number 928667413. The business is classified under holiday and other short-stay accommodation (NACE 55.200). The company was incorporated in 2022. Registered share capital is NOK 2.0m, divided into 2000 shares. The company's stated purpose is: “Utvikling og drift av ferieleiligheter og alt som står i naturlig forbindelse med dette, herunder direkte og indirekte investeringer i foretak som driver slik virksomhet.”. The most recent filed accounts, for the 2024 financial year, show NOK 4.4m in revenue and NOK −19,000 in operating profit.

Key figures · 2024

Revenue
NOK 4.4m
Operating profit
NOK −19,000
Equity
NOK 10.1m
Est. value
NOK 5.1m

Financial health · 2024

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

Who owns FURREHYTTER AS?

JOHNNY JOHANNES FURRE
FURREHYTTER AS
NOK 4.4m rev. · NOK −19,000 profit

FURREHYTTER AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about FURREHYTTER AS

Who owns FURREHYTTER AS?

JOHNNY JOHANNES FURRE is the largest registered owner, with 100.0%.

What is the revenue of FURREHYTTER AS?

FURREHYTTER AS had revenue of NOK 4.4m in 2024.

Who is the general manager of FURREHYTTER AS?

Johnny Johannes Furre is registered as general manager of FURREHYTTER AS.

Where is FURREHYTTER AS based?

FURREHYTTER AS has its business address in Sjernarøy.

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.