BIZTRAC BETA
COMPANY REGISTER PROFILE
985216649 ORG. NO. 2025 ACCOUNTS 8 SECTIONS
Active UPDATED 15.06.2026
Uoppgitt

ANDSLIMOEN VEISERVICE AS

Org. no. 985216649 Limited company (AS) Senja Incorporated 2002 Active
Ownership graph ↗
Operating profit NOK −7,000
Equity NOK 299,000
Incorporated 2002
Share capital NOK 203,000

Signals

1 flags
  • Driftsunderskudd 2025 Siste driftsresultat er negativt (−7k kr).

ANDSLIMOEN VEISERVICE AS is registered as a limited company in Senja, Troms with organisation number 985216649. The business is classified under uoppgitt (NACE 00.000). The company was incorporated in 2002. Registered share capital is NOK 203,000, divided into 406 shares. The company's stated purpose is: “Drive bensinstasjon og annen virksomhet som er naturlig å drive fra bensinstasjon. Selskapet kan gå inn med kapital i andre virksomheter.”.

Key figures · 2025

Operating profit
NOK −7,000
Equity
NOK 299,000
Est. value
NOK 352,000

Financial health · 2025

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

Who owns ANDSLIMOEN VEISERVICE AS?

ANDSLIMOEN VEISERVICE AS
ANDSLIMOEN VEISERVICE AS
· NOK −7,000 profit

ANDSLIMOEN VEISERVICE AS has 2 registered shareholders:

All shareholders and roles →

Which companies does ANDSLIMOEN VEISERVICE AS own?

ANDSLIMOEN VEISERVICE AS holds a stake in 1 company:

See the full ownership structure →

Frequently asked questions about ANDSLIMOEN VEISERVICE AS

Who owns ANDSLIMOEN VEISERVICE AS?

ANDSLIMOEN VEISERVICE AS is the largest registered owner, with 50.7%.

Who is the general manager of ANDSLIMOEN VEISERVICE AS?

Ole Svein Lauknes is registered as general manager of ANDSLIMOEN VEISERVICE AS.

Where is ANDSLIMOEN VEISERVICE AS based?

ANDSLIMOEN VEISERVICE AS has its business address in Finnsnes.

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.