biztrac. BETA
COMPANY REGISTER PROFILE
925554812 ORG. NO. 2025 ACCOUNTS 9 SECTIONS
Active UPDATED 03.10.2026
Buying and selling of own real estate

AWP EIENDOMSSELSKAP AS

Org. no. 925554812 Limited company (AS) Drammen Incorporated 2020 Active
Ownership graph ↗
Operating profit NOK −25,000
Equity NOK 15,000
Incorporated 2020
Share capital NOK 30,000

Signals

2 flags
  • Driftsunderskudd 2025 Siste driftsresultat er negativt (−25k kr).
  • Nylig endring 2026-09-08 Adresseendring registrert 2026-09-08.

AWP EIENDOMSSELSKAP AS is registered as a limited company in Drammen, Buskerud with organisation number 925554812. The business is classified under buying and selling of own real estate (NACE 68.110). The company was incorporated in 2020. Registered share capital is NOK 30,000, divided into 100 shares. The company's stated purpose is: “Kjøp, salg og drift av fast eiendom samt ved kjøp av aksjer eller på annen måte å delta i andre virksomheter.”.

Former names: GJ BYGGTJENESTER AS

Key figures · 2025

Operating profit
NOK −25,000
▼ −223 %
Equity
NOK 15,000
▼ −62 %
Est. value
NOK 14,000

Financial health · 2025

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

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

Who owns AWP EIENDOMSSELSKAP AS?

AWP EIENDOMSSELSKAP AS
· NOK −25,000 profit

AWP EIENDOMSSELSKAP AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about AWP EIENDOMSSELSKAP AS

Who owns AWP EIENDOMSSELSKAP AS?

Arne Giske is the largest registered owner, with 100.0%.

Who is the general manager of AWP EIENDOMSSELSKAP AS?

Ole Hallvard Haugen is registered as general manager of AWP EIENDOMSSELSKAP AS.

Where is AWP EIENDOMSSELSKAP AS based?

AWP EIENDOMSSELSKAP AS has its business address in Svelvik.

Source: Biztrac.no · Data from the Brønnøysund Register Centre and the Norwegian Tax Administration · Last updated 03.10.2026.

Report a problem

Found a technical fault, or something wrong in the data? Tell us what happened.