biztrac. BETA
COMPANY REGISTER PROFILE
864287042 ORG. NO. 2025 ACCOUNTS 8 SECTIONS
Active UPDATED 03.10.2026
Retail sale of books

SKJELDESTAD KONTORSPAR AS

Org. no. 864287042 Limited company (AS) Sogndal Incorporated 1992 Active
Revenue 2025 NOK 8.7m
Operating profit NOK −222,000
Equity NOK 1.8m
Incorporated 1992
Share capital NOK 1.3m

Signals

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

SKJELDESTAD KONTORSPAR AS is registered as a limited company in Sogndal, Vestland with organisation number 864287042. The business is classified under retail sale of books (NACE 47.610). The company was incorporated in 1992. Registered share capital is NOK 1.3m, divided into 370 shares. The company's stated purpose is: “Drive handel med papir og kontorutstyr og det hva hermed står i forbindelse.”. The most recent filed accounts, for the 2025 financial year, show NOK 8.7m in revenue and NOK −222,000 in operating profit.

Former names: O J SKJELDESTAD BOK OG PAPIRHANDEL AS

Key figures · 2025

Revenue
NOK 8.7m
▼ −3 %
Operating profit
NOK −222,000
▼ −371 %
Equity
NOK 1.8m
▼ −13 %
Est. value
NOK 3.7m

Financial health · 2025

Liquidity
2.83
Very good
Current assets ÷ current liabilities
Profitability
-7.9%
Not satisfactory
Return on total assets
Solidity
66.4%
Very good
Equity as a share of total capital

Who owns SKJELDESTAD KONTORSPAR AS?

SKJELDESTAD KONTORSPAR AS
NOK 8.7m rev. · NOK −222,000 profit

SKJELDESTAD KONTORSPAR AS has 2 registered shareholders:

All shareholders and roles →

Frequently asked questions about SKJELDESTAD KONTORSPAR AS

Who owns SKJELDESTAD KONTORSPAR AS?

Vidar Walsvik is the largest registered owner, with 90.0%.

What is the revenue of SKJELDESTAD KONTORSPAR AS?

SKJELDESTAD KONTORSPAR AS had revenue of NOK 8.7m in 2025.

Where is SKJELDESTAD KONTORSPAR AS based?

SKJELDESTAD KONTORSPAR AS has its business address in Sogndal.

Source: Biztrac.no · Data from the Brønnøysund Register Centre and the Norwegian Tax Administration · Last updated 03.10.2026.

Report a problem

Found a technical fault, or something wrong in the data? Tell us what happened.