BIZTRAC BETA
Activities of tour guides

GUIDED FJORD ADVENTURES AS

Org. no. 932498448 Limited company (AS) Bergen Incorporated 2024 Active
Ownership graph ↗
Revenue 2024 NOK 725,000
Operating profit NOK 127,000
Equity NOK 117,000
Incorporated 2024
Employees 16
Share capital NOK 30,000

GUIDED FJORD ADVENTURES AS is registered as a limited company in Bergen, Vestland with organisation number 932498448. The business is classified under activities of tour guides (NACE 79.902). The company was incorporated in 2024 and has 16 registered employees. Registered share capital is NOK 30,000, divided into 30000 shares. The company's stated purpose is: “Tilby guide- og reiseledertjenester, herunder, men ikke begrenset til, omvisninger, turplanlegging, koordinering av reiseaktiviteter og formidling av informasjon om lokale attraksjoner, historie og kultur.”. The most recent filed accounts, for the 2024 financial year, show NOK 725,000 in revenue and NOK 127,000 in operating profit.

Key figures · 2024

Revenue
NOK 725,000
Operating profit
NOK 127,000
Equity
NOK 117,000
Est. value
NOK 361,000

Financial health · 2024

Liquidity
0.82
Weak
Current assets ÷ current liabilities
Profitability
Not available
Return on total assets
Solidity
8.5%
Weak
Equity as a share of total capital

Who owns GUIDED FJORD ADVENTURES AS?

TAHA JAMAL BILBAS
GUIDED FJORD ADVENTURES AS
NOK 725,000 rev. · NOK 127,000 profit

GUIDED FJORD ADVENTURES AS has 2 registered shareholders:

All shareholders and roles →

Frequently asked questions about GUIDED FJORD ADVENTURES AS

Who owns GUIDED FJORD ADVENTURES AS?

TAHA JAMAL BILBAS is the largest registered owner, with 50.0%.

What is the revenue of GUIDED FJORD ADVENTURES AS?

GUIDED FJORD ADVENTURES AS had revenue of NOK 725,000 in 2024.

Where is GUIDED FJORD ADVENTURES AS based?

GUIDED FJORD ADVENTURES AS has its business address in Blomsterdalen.

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.