BIZTRAC BETA
Construction of residential and non-residential buildings

VRENNE BYGG AS

Org. no. 999058027 Limited company (AS) Nore Og Uvdal Incorporated 2012 Active
Ownership graph ↗
Revenue 2025 NOK 77,000
Operating profit NOK 563
Equity NOK 44,000
Incorporated 2012
Share capital NOK 30,000

VRENNE BYGG AS is registered as a limited company in Nore Og Uvdal, Buskerud with organisation number 999058027. The business is classified under construction of residential and non-residential buildings (NACE 41.000). The company was incorporated in 2012. Registered share capital is NOK 30,000, divided into 300 shares. The company's stated purpose is: “Yte håndverkstjenester innen bygg og anlegg, oppføring og salg av eiendommer, drift og forvaltning av eiendom, samt annen virksomhet tilknyttet dette, herunder deltakelse i andre selskaper.”. The most recent filed accounts, for the 2025 financial year, show NOK 77,000 in revenue and NOK 563 in operating profit.

Key figures · 2025

Revenue
NOK 77,000
Operating profit
NOK 563
Equity
NOK 44,000
Est. value
NOK 21,000

Financial health · 2025

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

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

Who owns VRENNE BYGG AS?

TORE VRENNE
VRENNE BYGG AS
NOK 77,000 rev. · NOK 563 profit

VRENNE BYGG AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about VRENNE BYGG AS

Who owns VRENNE BYGG AS?

TORE VRENNE is the largest registered owner, with 100.0%.

What is the revenue of VRENNE BYGG AS?

VRENNE BYGG AS had revenue of NOK 77,000 in 2025.

Who is the general manager of VRENNE BYGG AS?

Tore Vrenne is registered as general manager of VRENNE BYGG AS.

Where is VRENNE BYGG AS based?

VRENNE BYGG AS has its business address in Rødberg.

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.