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

VENNEBYGG & EIENDOM AS

Org. no. 925927252 Limited company (AS) Fredrikstad Incorporated 2020 Active
Ownership graph ↗
Operating profit NOK −9,000
Equity NOK −94,000
Incorporated 2020
Share capital NOK 100,000

Signals

2 flags
  • Negativ egenkapital 2025 Bokført egenkapital er negativ (−94k kr).
  • Driftsunderskudd 2025 Siste driftsresultat er negativt (−9k kr).

VENNEBYGG & EIENDOM AS is registered as a limited company in Fredrikstad, Østfold with organisation number 925927252. 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 100,000, divided into 100 shares. The company's stated purpose is: “Selskapet skal drive med bygg, påbygg, nybygg, kjøp og salg av eiendom og andre produkter og tjenester som naturlig faller sammen med dette.”.

Key figures · 2025

Operating profit
NOK −9,000
▲ +78 %
Equity
NOK −94,000
▼ −11 %

Financial health · 2025

Liquidity
–
Not available
Current assets ÷ current liabilities
Profitability
-0.4%
Not satisfactory
Return on total assets
Solidity
-3.9%
Weak
Equity as a share of total capital

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

Who owns VENNEBYGG & EIENDOM AS?

VENNEBYGG & EIENDOM AS has 2 registered shareholders:

All shareholders and roles →

Frequently asked questions about VENNEBYGG & EIENDOM AS

Who owns VENNEBYGG & EIENDOM AS?

TORSNES EIENDOMSSELSKAP AS is the largest registered owner, with 50.0%.

Who is the general manager of VENNEBYGG & EIENDOM AS?

Knut Johan Ileby Gulbrandsen is registered as general manager of VENNEBYGG & EIENDOM AS.

Where is VENNEBYGG & EIENDOM AS based?

VENNEBYGG & EIENDOM AS has its business address in Fredrikstad.

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.