BIZTRAC BETA
Other captive investment companies

GOOSEBERRY AS

Org. no. 916740263 Limited company (AS) Bjørnafjorden Incorporated 2016 Active
Ownership graph ↗
Revenue 2024 NOK 0
Operating profit NOK −2,000
Equity NOK 467,000
Incorporated 2016
Share capital NOK 45,000

Signals

1 flags
  • Driftsunderskudd 2024 Siste driftsresultat er negativt (−2k kr).

GOOSEBERRY AS is registered as a limited company in Bjørnafjorden, Vestland with organisation number 916740263. The business is classified under other captive investment companies (NACE 64.323). The company was incorporated in 2016. Registered share capital is NOK 45,000, divided into 1000 shares. The company's stated purpose is: “Investeringer og annet som naturlig faller sammen med dette, herunder å delta i andre selskaper med lignende virksomhet, kjøp og salg av aksjer, eller på annen måte gjøre seg interessert i andre foretagender.”. The most recent filed accounts, for the 2024 financial year, show NOK 0 in revenue and NOK −2,000 in operating profit.

Key figures · 2024

Revenue
NOK 0
Operating profit
NOK −2,000
Equity
NOK 467,000
Est. value
NOK 426,000

Financial health · 2024

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

Who owns GOOSEBERRY AS?

OLAV SKOGEN
GOOSEBERRY AS
NOK 0 rev. · NOK −2,000 profit

GOOSEBERRY AS has 1 registered shareholder:

All shareholders and roles →

Which companies does GOOSEBERRY AS own?

GOOSEBERRY AS holds a stake in 1 company:

See the full ownership structure →

Frequently asked questions about GOOSEBERRY AS

Who owns GOOSEBERRY AS?

OLAV SKOGEN is the largest registered owner, with 100.0%.

What is the revenue of GOOSEBERRY AS?

GOOSEBERRY AS had revenue of NOK 0 in 2024.

Where is GOOSEBERRY AS based?

GOOSEBERRY AS has its business address in Os.

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.