BIZTRAC BETA
COMPANY REGISTER PROFILE
935991528 ORG. NO. 8 SECTIONS
Bankrupt UPDATED 02.09.2026
PRINT W AS is registered as “Bankrupt” with the Brønnøysund Register Centre.
Activities of advertising agencies

PRINT W AS

Org. no. 935991528 Limited company (AS) Osterøy Incorporated 2025 Bankrupt
Ownership graph ↗
Incorporated 2025
Share capital NOK 30,000

Signals

3 flags
  • Konkurs Selskapet er registrert konkurs i Enhetsregisteret.
  • Mangler regnskap Ingen årsregnskap er registrert for selskapet.
  • Nylig endring 2026-05-02 Konkurs registrert 2026-05-02.

PRINT W AS is registered as a limited company in Osterøy, Vestland with organisation number 935991528. The business is classified under activities of advertising agencies (NACE 73.110). The company was incorporated in 2025. Registered share capital is NOK 30,000, divided into 300 shares. The company's stated purpose is: “Foliering, kjøp, salg, produksjon og montering av reklamemateriell, samt alt som naturlig har sammenheng med dette.”.

Former names: JANAS WRAP & PRINT AS

Who owns PRINT W AS?

PRINT W AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about PRINT W AS

Who owns PRINT W AS?

WORRTEKK AS is the largest registered owner, with 100.0%.

Who is the general manager of PRINT W AS?

Tore Worren is registered as general manager of PRINT W AS.

Where is PRINT W AS based?

PRINT W AS has its business address in Valestrandsfossen.

Property

Business address c/o Worrtekk As Hamrenesvegen 68, 5281 Valestrandsfossen
Cadastral unit 4630-135/42/0/0
Building Enebolig · 1 unit

3 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.