BIZTRAC BETA
COMPANY REGISTER PROFILE
936452132 ORG. NO. 2025 ACCOUNTS 7 SECTIONS
Active UPDATED 02.09.2026
Uoppgitt

SKOTTINDEN AS

Org. no. 936452132 Limited company (AS) Vestvågøy Incorporated 2025 Active
Ownership graph ↗
Equity NOK 5.7m
Incorporated 2025
Share capital NOK 95,000

SKOTTINDEN AS is registered as a limited company in Vestvågøy, Nordland with organisation number 936452132. The business is classified under uoppgitt (NACE 00.000). The company was incorporated in 2025. Registered share capital is NOK 95,000, divided into 100 shares. The company's stated purpose is: “Å erverve næringsvirksomhet gjennom kjøp og salg av selskapsandeler og/eller kjøp og salg av eiendeler, rettigheter og forpliktelser, samt alt som hermed er forbundet.”.

Key figures · 2025

Equity
NOK 5.7m
Est. value
NOK 6.7m

Financial health · 2025

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

Who owns SKOTTINDEN AS?

SKOTTINDEN AS has 1 registered shareholder:

All shareholders and roles →

Which companies does SKOTTINDEN AS own?

SKOTTINDEN AS holds a stake in 1 company:

See the full ownership structure →

Frequently asked questions about SKOTTINDEN AS

Who owns SKOTTINDEN AS?

LARS ÅSBERG BØE is the largest registered owner, with 100.0%.

Where is SKOTTINDEN AS based?

SKOTTINDEN AS has its business address in Ballstad.

Property

Business address Øyaveien 51A, 8373 Ballstad
Cadastral unit 1860-10/235/0/0
Building Hytter, sommerhus ol fritidsbygning · 1 unit

2 companies are registered at this address.

The address this company is registered at, from the company register and matched against the cadastre. It does not say who owns the property — a company may be a tenant, and the address is often its accountant's. Source: Brønnøysundregistrene and © Kartverket.

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.