BIZTRAC BETA
COMPANY REGISTER PROFILE
933971430 ORG. NO. 2025 ACCOUNTS 7 SECTIONS
Active UPDATED 15.06.2026
Other real estate activities on a fee or contract basis

STYREVERN AS

Org. no. 933971430 Limited company (AS) Vennesla Incorporated 2024 Active
Ownership graph ↗
Operating profit NOK −3,000
Equity NOK 21,000
Incorporated 2024
Share capital NOK 30,000

Signals

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

STYREVERN AS is registered as a limited company in Vennesla, Agder with organisation number 933971430. The business is classified under other real estate activities on a fee or contract basis (NACE 68.320). The company was incorporated in 2024. Registered share capital is NOK 30,000, divided into 10 shares. The company's stated purpose is: “Støtte til styret i sameier og borettslag, herunder management for hire, innhenting av juridisk og byggeteknisk kompetanse. Ettårs- og femårs kontroll av boligsameier. Coaching og rådgivning. Operativ drift. Strategi. Kommunikasjon intern og ekstern.”.

Key figures · 2025

Operating profit
NOK −3,000
Equity
NOK 21,000
Est. value
NOK 19,000

Financial health · 2025

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

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

Who owns STYREVERN AS?

ENA CATHRINE CATHY QUIST
STYREVERN AS
· NOK −3,000 profit

STYREVERN AS has 2 registered shareholders:

All shareholders and roles →

Frequently asked questions about STYREVERN AS

Who owns STYREVERN AS?

ENA CATHRINE CATHY QUIST is the largest registered owner, with 90.0%.

Who is the general manager of STYREVERN AS?

Ena Cathrine Cathy Quist is registered as general manager of STYREVERN AS.

Where is STYREVERN AS based?

STYREVERN AS has its business address in Vennesla.

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.