BIZTRAC BETA
Holiday and other short-stay accommodation

FJORD CASITAS AS

Org. no. 929781252 Limited company (AS) Bergen Incorporated 2022 Active
Ownership graph ↗
Revenue 2024 NOK 143,000
Operating profit NOK 103,000
Equity NOK −1.5m
Incorporated 2022
Share capital NOK 30,000

Signals

1 flags
  • Negativ egenkapital 2024 Bokført egenkapital er negativ (−1,5 mill kr).

FJORD CASITAS AS is registered as a limited company in Bergen, Vestland with organisation number 929781252. 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 30,000, divided into 10 shares. The company's stated purpose is: “Kjøp, salg og utleie av fast eindom.”. The most recent filed accounts, for the 2024 financial year, show NOK 143,000 in revenue and NOK 103,000 in operating profit.

Key figures · 2024

Revenue
NOK 143,000
Operating profit
NOK 103,000
Equity
NOK −1.5m
Est. value
NOK 418,000

Financial health · 2024

Liquidity
1.34
Satisfactory
Current assets ÷ current liabilities
Profitability
Not available
Return on total assets
Solidity
-28.5%
Weak
Equity as a share of total capital

Solidity capped at Weak because equity is below NOK 100,000.

Who owns FJORD CASITAS AS?

SERGIO CASTILLO VICENTE
FJORD CASITAS AS
NOK 143,000 rev. · NOK 103,000 profit

FJORD CASITAS AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about FJORD CASITAS AS

Who owns FJORD CASITAS AS?

SERGIO CASTILLO VICENTE is the largest registered owner, with 100.0%.

What is the revenue of FJORD CASITAS AS?

FJORD CASITAS AS had revenue of NOK 143,000 in 2024.

Who is the general manager of FJORD CASITAS AS?

Sergio Castillo Vicente is registered as general manager of FJORD CASITAS AS.

Where is FJORD CASITAS AS based?

FJORD CASITAS AS has its business address in Bergen.

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.