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

WAYNECORP AS

Org. no. 926064118 Limited company (AS) Sandnes Incorporated 2020 Active
Ownership graph ↗
Operating profit NOK −1,000
Equity NOK 708,000
Incorporated 2020
Share capital NOK 30,000

Signals

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

WAYNECORP AS is registered as a limited company in Sandnes, Rogaland with organisation number 926064118. The business is classified under uoppgitt (NACE 00.000). The company was incorporated in 2020. Registered share capital is NOK 30,000, divided into 1000 shares. The company's stated purpose is: “Investering.”.

Key figures · 2025

Operating profit
NOK −1,000
▼ −106 %
Equity
NOK 708,000
▼ −12 %
Est. value
NOK 411,000

Financial health · 2025

Liquidity
56.90
Very good
Current assets ÷ current liabilities
Profitability
46.6%
Very good
Return on total assets
Solidity
31.9%
Good
Equity as a share of total capital

Who owns WAYNECORP AS?

WAYNECORP AS
· NOK −1,000 profit

WAYNECORP AS has 1 registered shareholder:

All shareholders and roles →

Which companies does WAYNECORP AS own?

WAYNECORP AS holds stakes in 2 companies:

See the full ownership structure →

Frequently asked questions about WAYNECORP AS

Who owns WAYNECORP AS?

SEBASTIAN WHITE is the largest registered owner, with 100.0%.

Where is WAYNECORP AS based?

WAYNECORP AS has its business address in Sandnes.

Property

Business address c/o Sebastian White Reinsdyrveien 20A, 4323 Sandnes
Cadastral unit 1108-47/1352/0/0
Building Enebolig · 1 unit

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.