BIZTRAC BETA
COMPANY REGISTER PROFILE
999145760 ORG. NO. 2025 ACCOUNTS 7 SECTIONS
Active UPDATED 02.09.2026
Development of building projects

FERJEVEIEN BRYGGE AS

Org. no. 999145760 Limited company (AS) Farsund Incorporated 2012 Active
Ownership graph ↗
Operating profit NOK −33,000
Equity NOK −219,000
Incorporated 2012
Share capital NOK 30,000

Signals

3 flags
  • Negativ egenkapital 2025 Bokført egenkapital er negativ (−219k kr).
  • Driftsunderskudd 2025 Siste driftsresultat er negativt (−33k kr).
  • Ingen revisor Selskapet har ingen registrert revisor. Vanlig for små AS som har valgt bort revisjon, men verdt å merke seg.

FERJEVEIEN BRYGGE AS is registered as a limited company in Farsund, Agder with organisation number 999145760. The business is classified under development of building projects (NACE 68.120). The company was incorporated in 2012. Registered share capital is NOK 30,000, divided into 30 shares. The company's stated purpose is: “Erverve, utvikle, eie, drifte og selge fast eiendom enten direkte eller ved andeler i andre selskaper, samt å drive annen virksomhet som står i forbindelse med dette.”.

Key figures · 2025

Operating profit
NOK −33,000
▼ −2 %
Equity
NOK −219,000
▼ −18 %

Financial health · 2025

Liquidity
0.02
Not satisfactory
Current assets ÷ current liabilities
Profitability
Not available
Return on total assets
Solidity
-5187.1%
Weak
Equity as a share of total capital

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

Who owns FERJEVEIEN BRYGGE AS?

FERJEVEIEN BRYGGE AS
· NOK −33,000 profit

FERJEVEIEN BRYGGE AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about FERJEVEIEN BRYGGE AS

Who owns FERJEVEIEN BRYGGE AS?

FARSUND VEKST AS is the largest registered owner, with 100.0%.

Where is FERJEVEIEN BRYGGE AS based?

FERJEVEIEN BRYGGE AS has its business address in Farsund.

Source: Biztrac.no · Data from the Brønnøysund Register Centre and the Norwegian Tax Administration · Last updated 02.09.2026.

Report a problem

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