BIZTRAC BETA
Other real estate activities on a fee or contract basis

GOBO DRIFT AS

Org. no. 992247436 Limited company (AS) Øygarden Incorporated 2008 Active
Ownership graph ↗
Revenue 2025 NOK 3.5m
Operating profit NOK 1,000
Equity NOK 205,000
Incorporated 2008
Employees 7
Share capital NOK 100,000

Signals

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

GOBO DRIFT AS is registered as a limited company in Øygarden, Vestland with organisation number 992247436. The business is classified under other real estate activities on a fee or contract basis (NACE 68.320). The company was incorporated in 2008 and has 7 registered employees. Registered share capital is NOK 100,000, divided into 100 shares. The company's stated purpose is: “Kjøp og salg av eiendom, samt drift av denne. Utvikling av eiendommer og bygg, samt utbygging av eiendommer og generelt bygningsarbeid. I tillegg deltakelse i selskaper.”. The most recent filed accounts, for the 2025 financial year, show NOK 3.5m in revenue and NOK 1,000 in operating profit.

Key figures · 2025

Revenue
NOK 3.5m
Operating profit
NOK 1,000
Equity
NOK 205,000
Est. value
NOK 146,000

Financial health · 2025

Liquidity
1.21
Satisfactory
Current assets ÷ current liabilities
Profitability
Not available
Return on total assets
Solidity
17.6%
Satisfactory
Equity as a share of total capital

Who owns GOBO DRIFT AS?

GOBO EIENDOM AS
GOBO DRIFT AS
NOK 3.5m rev. · NOK 1,000 profit

GOBO DRIFT AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about GOBO DRIFT AS

Who owns GOBO DRIFT AS?

GOBO EIENDOM AS is the largest registered owner, with 100.0%.

What is the revenue of GOBO DRIFT AS?

GOBO DRIFT AS had revenue of NOK 3.5m in 2025.

Where is GOBO DRIFT AS based?

GOBO DRIFT AS has its business address in Knarrevik.

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.