BIZTRAC BETA
COMPANY REGISTER PROFILE
937296487 ORG. NO. 7 SECTIONS
Active UPDATED 02.09.2026
Buying and selling of own real estate

KVINEN EIENDOMSELSKAP AS

Org. no. 937296487 Limited company (AS) Hægebostad Incorporated 2026 Active
Ownership graph ↗
Incorporated 2026
Share capital NOK 30,000

Signals

2 flags
  • Mangler regnskap Ingen årsregnskap er registrert for selskapet.
  • Nystiftet selskap Selskapet ble stiftet 2026-02-20.

KVINEN EIENDOMSELSKAP AS is registered as a limited company in Hægebostad, Agder with organisation number 937296487. The business is classified under buying and selling of own real estate (NACE 68.110). The company was incorporated in 2026. Registered share capital is NOK 30,000, divided into 30 shares. The company's stated purpose is: “Kjøp, salg, utvikling, drift og utleie av fast eiendom, samt investering i aksjer/andeler i andre selskaper med tilsvarende virksomhet.”.

Who owns KVINEN EIENDOMSELSKAP AS?

No shareholders are registered for KVINEN EIENDOMSELSKAP AS in open Norwegian sources. Shareholder data exists mainly for limited companies (AS/ASA).

Group structure

KVINEN EIENDOMSELSKAP AS er morselskap for 2 datterselskaper:

Frequently asked questions about KVINEN EIENDOMSELSKAP AS

Who is the general manager of KVINEN EIENDOMSELSKAP AS?

Espen Kvinen is registered as general manager of KVINEN EIENDOMSELSKAP AS.

Where is KVINEN EIENDOMSELSKAP AS based?

KVINEN EIENDOMSELSKAP AS has its business address in Tingvatn.

Property

Business address Naglestadveien 79, 4595 Tingvatn
Cadastral unit 4226-45/4/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.