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

WILFRO AS

Org. no. 933377962 Limited company (AS) Nesodden Incorporated 2024 Active
Ownership graph ↗
Operating profit NOK −15,000
Equity NOK 946,000
Incorporated 2024
Share capital NOK 38,000

Signals

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

WILFRO AS is registered as a limited company in Nesodden, Akershus with organisation number 933377962. The business is classified under uoppgitt (NACE 00.000). The company was incorporated in 2024. Registered share capital is NOK 38,000, divided into 76 shares. The company's stated purpose is: “Å investere i aksjer og andre finansielle instrumenter, deltakelse i andre selskaper og konsulentvirksomhet.”.

Key figures · 2025

Operating profit
NOK −15,000
Equity
NOK 946,000
Est. value
NOK 600,000

Financial health · 2025

Liquidity
32.49
Very good
Current assets ÷ current liabilities
Profitability
Not available
Return on total assets
Solidity
89.3%
Very good
Equity as a share of total capital

Who owns WILFRO AS?

WILFRO AS
· NOK −15,000 profit

WILFRO AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about WILFRO AS

Who owns WILFRO AS?

WILLIAM BERDINES FRØYLAND WIIK is the largest registered owner, with 100.0%.

Where is WILFRO AS based?

WILFRO AS has its business address in Bjørnemyr.

Property

Business address Steinveien 14, 1453 Bjørnemyr
Cadastral unit 3212-1/417/0/0
Building Stort frittliggende boligbygg på 3 og 4 etg · 8 units

8 companies are registered at this address.

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.