biztrac. BETA
COMPANY REGISTER PROFILE
928236099 ORG. NO. 2025 ACCOUNTS 8 SECTIONS
Active UPDATED 03.10.2026
Retail sale of footwear and leather goods

HEIE SKO AS

Org. no. 928236099 Limited company (AS) Fredrikstad Incorporated 2021 Active
Ownership graph ↗
Revenue 2025 NOK 2.6m
Operating profit NOK 37,000
Equity NOK 1.4m
Incorporated 2021
Share capital NOK 100,000

HEIE SKO AS is registered as a limited company in Fredrikstad, Østfold with organisation number 928236099. The business is classified under retail sale of footwear and leather goods (NACE 47.720). The company was incorporated in 2021. Registered share capital is NOK 100,000, divided into 100000 shares. The company's stated purpose is: “Salg av sko i butikk, samt annet som faller naturlig herunder. Selskapet kan også investere i andre selskaper, herunder kjøp og salg av aksjer eller på annen måte gjøre seg interessert i andre foretak.”. The most recent filed accounts, for the 2025 financial year, show NOK 2.6m in revenue and NOK 37,000 in operating profit.

Key figures · 2025

Revenue
NOK 2.6m
▼ −5 %
Operating profit
NOK 37,000
▼ −48 %
Equity
NOK 1.4m
▲ +2 %
Est. value
NOK 879,000

Financial health · 2025

Liquidity
6.75
Very good
Current assets ÷ current liabilities
Profitability
2.3%
Weak
Return on total assets
Solidity
85.2%
Very good
Equity as a share of total capital

Who owns HEIE SKO AS?

HEIE SKO AS
NOK 2.6m rev. · NOK 37,000 profit

HEIE SKO AS has 2 registered shareholders:

All shareholders and roles →

Frequently asked questions about HEIE SKO AS

Who owns HEIE SKO AS?

Stine Heie Veiby is the largest registered owner, with 50.0%.

What is the revenue of HEIE SKO AS?

HEIE SKO AS had revenue of NOK 2.6m in 2025.

Who is the general manager of HEIE SKO AS?

Stine Heie Veiby is registered as general manager of HEIE SKO AS.

Where is HEIE SKO AS based?

HEIE SKO AS has its business address in Sellebakk.

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.