BIZTRAC BETA
Retail sale of other new goods

FJORDBUDA STAVANGER AS

Org. no. 921584334 Limited company (AS) Ålesund Incorporated 2018 Active
Ownership graph ↗
Revenue 2024 NOK 59.4m
Operating profit NOK 16.8m
Equity NOK 30.4m
Incorporated 2018
Employees 38
Share capital NOK 102,000

Signals

1 flags
  • Ingen revisor Selskapet har ingen registrert revisor. Vanlig for små AS som har valgt bort revisjon, men verdt å merke seg.

FJORDBUDA STAVANGER AS is registered as a limited company in Ålesund, Møre og Romsdal with organisation number 921584334. The business is classified under retail sale of other new goods (NACE 47.780). The company was incorporated in 2018 and has 38 registered employees. Registered share capital is NOK 102,000, divided into 102 shares. The company's stated purpose is: “Handel og annen service rettet mot turistnæringen, samt det som naturlig står i tilknytning til dette.”. The most recent filed accounts, for the 2024 financial year, show NOK 59.4m in revenue and NOK 16.8m in operating profit.

Key figures · 2024

Revenue
NOK 59.4m
Operating profit
NOK 16.8m
Equity
NOK 30.4m
Est. value
NOK 72.6m

Financial health · 2024

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

Who owns FJORDBUDA STAVANGER AS?

VINJENAUSTET HOLDING AS
FJORDBUDA STAVANGER AS
NOK 59.4m rev. · NOK 16.8m profit

FJORDBUDA STAVANGER AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about FJORDBUDA STAVANGER AS

Who owns FJORDBUDA STAVANGER AS?

VINJENAUSTET HOLDING AS is the largest registered owner, with 100.0%.

What is the revenue of FJORDBUDA STAVANGER AS?

FJORDBUDA STAVANGER AS had revenue of NOK 59.4m in 2024.

Where is FJORDBUDA STAVANGER AS based?

FJORDBUDA STAVANGER 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 15.06.2026.

Report a problem

Found a technical fault, or something wrong in the data? Tell us what happened.