biztrac. BETA
COMPANY REGISTER PROFILE
932683261 ORG. NO. 2025 ACCOUNTS 7 SECTIONS
In liquidation UPDATED 03.10.2026
⚠SKO DÆ AS is registered as “In liquidation” with the Brønnøysund Register Centre.
Retail sale of footwear and leather goods

SKO DÆ AS

Org. no. 932683261 Limited company (AS) Balsfjord Incorporated 2023 In liquidation
Revenue 2025 NOK 1.8m
Operating profit NOK 127,000
Equity NOK 392,000
Incorporated 2023
Share capital NOK 60,000

Signals

1 flags
  • Under avvikling Selskapet er under frivillig avvikling.

SKO DÆ AS is registered as a limited company in Balsfjord, Troms with organisation number 932683261. The business is classified under retail sale of footwear and leather goods (NACE 47.720). The company was incorporated in 2023. Registered share capital is NOK 60,000, divided into 60 shares. The company's stated purpose is: “Butikkhandel med skotøy og tilbehør til skotøy.”. The most recent filed accounts, for the 2025 financial year, show NOK 1.8m in revenue and NOK 127,000 in operating profit.

Key figures · 2025

Revenue
NOK 1.8m
▲ +5 %
Operating profit
NOK 127,000
▼ −62 %
Equity
NOK 392,000
▲ +27 %
Est. value
NOK 756,000

Financial health · 2025

Liquidity
1.26
Satisfactory
Current assets ÷ current liabilities
Profitability
8.4%
Satisfactory
Return on total assets
Solidity
20.4%
Good
Equity as a share of total capital

Who owns SKO DÆ AS?

SKO DÆ AS
NOK 1.8m rev. · NOK 127,000 profit

SKO DÆ AS has 2 registered shareholders:

All shareholders and roles →

Frequently asked questions about SKO DÆ AS

Who owns SKO DÆ AS?

Lasse Pedersen is the largest registered owner, with 50.0%.

What is the revenue of SKO DÆ AS?

SKO DÆ AS had revenue of NOK 1.8m in 2025.

Who is the general manager of SKO DÆ AS?

Inger-Dalena Johansen is registered as general manager of SKO DÆ AS.

Where is SKO DÆ AS based?

SKO DÆ AS has its business address in Storsteinnes.

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.