BIZTRAC BETA
Retail sale of automotive fuel

GULSVIK SERVICESENTER AS

Org. no. 999523919 Limited company (AS) Flå Incorporated 2012 Active
Ownership graph ↗
Operating profit NOK −1.8m
Equity NOK −216,000
Incorporated 2012
Share capital NOK 100,000

Signals

2 flags
  • Negativ egenkapital 2024 Bokført egenkapital er negativ (−216k kr).
  • Driftsunderskudd 2024 Siste driftsresultat er negativt (−1,8 mill kr).

GULSVIK SERVICESENTER AS is registered as a limited company in Flå, Buskerud with organisation number 999523919. The business is classified under retail sale of automotive fuel (NACE 47.300). The company was incorporated in 2012. Registered share capital is NOK 100,000, divided into 100 shares. The company's stated purpose is: “Drive handel og alt som står i forbindelse hermed. Selskapets primære formål er å drive bensinstasjon.”.

Key figures · 2024

Operating profit
NOK −1.8m
Equity
NOK −216,000

Financial health · 2024

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

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

Who owns GULSVIK SERVICESENTER AS?

Anette Aas Karlsen
GULSVIK SERVICESENTER AS
· NOK −1.8m profit

GULSVIK SERVICESENTER AS has 1 registered shareholder:

All shareholders and roles →

Which companies does GULSVIK SERVICESENTER AS own?

GULSVIK SERVICESENTER AS holds a stake in 1 company:

See the full ownership structure →

Frequently asked questions about GULSVIK SERVICESENTER AS

Who owns GULSVIK SERVICESENTER AS?

Anette Aas Karlsen is the largest registered owner, with 100.0%.

Who is the general manager of GULSVIK SERVICESENTER AS?

Anette Aas Karlsen is registered as general manager of GULSVIK SERVICESENTER AS.

Where is GULSVIK SERVICESENTER AS based?

GULSVIK SERVICESENTER AS has its business address in Flå.

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.