BIZTRAC BETA
Other non-specialised retail sale

WILD SUPPLY AS

Org. no. 923697586 Limited company (AS) Askøy Incorporated 2019 Active
Ownership graph ↗
Revenue 2024 NOK 2.7m
Operating profit NOK 267,000
Equity NOK −407,000
Incorporated 2019
Share capital NOK 30,000

Signals

1 flags
  • Negativ egenkapital 2024 Bokført egenkapital er negativ (−407k kr).

WILD SUPPLY AS is registered as a limited company in Askøy, Vestland with organisation number 923697586. The business is classified under other non-specialised retail sale (NACE 47.120). The company was incorporated in 2019. Registered share capital is NOK 30,000, divided into 30 shares. The company's stated purpose is: “Import, kjøp og salg av varer både på nett og direkte salg samt alt annet som faller naturlig innunder dette.”. The most recent filed accounts, for the 2024 financial year, show NOK 2.7m in revenue and NOK 267,000 in operating profit.

Key figures · 2024

Revenue
NOK 2.7m
Operating profit
NOK 267,000
Equity
NOK −407,000
Est. value
NOK 1.4m

Financial health · 2024

Liquidity
0.43
Not satisfactory
Current assets ÷ current liabilities
Profitability
Not available
Return on total assets
Solidity
-92.1%
Weak
Equity as a share of total capital

Solidity capped at Weak because equity is below NOK 100,000.

Who owns WILD SUPPLY AS?

THOMAS IVERSEN
WILD SUPPLY AS
NOK 2.7m rev. · NOK 267,000 profit

WILD SUPPLY AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about WILD SUPPLY AS

Who owns WILD SUPPLY AS?

THOMAS IVERSEN is the largest registered owner, with 100.0%.

What is the revenue of WILD SUPPLY AS?

WILD SUPPLY AS had revenue of NOK 2.7m in 2024.

Who is the general manager of WILD SUPPLY AS?

Thomas Iversen is registered as general manager of WILD SUPPLY AS.

Where is WILD SUPPLY AS based?

WILD SUPPLY AS has its business address in Hauglandshella.

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.