biztrac. BETA
COMPANY REGISTER PROFILE
911553031 ORG. NO. 2025 ACCOUNTS 8 SECTIONS
In liquidation UPDATED 03.10.2026
⚠BRØDRENE UV AS is registered as “In liquidation” with the Brønnøysund Register Centre.
Construction of residential and non-residential buildings

BRØDRENE UV AS

Org. no. 911553031 Limited company (AS) Nes Incorporated 2013 In liquidation
Revenue 2025 NOK 2.3m
Operating profit NOK −62,000
Equity NOK 22,000
Incorporated 2013
Share capital NOK 30,000

Signals

1 flags
  • Under avvikling Selskapet er under frivillig avvikling.

BRØDRENE UV AS is registered as a limited company in Nes, Akershus with organisation number 911553031. The business is classified under construction of residential and non-residential buildings (NACE 41.000). The company was incorporated in 2013. Registered share capital is NOK 30,000, divided into 100 shares. The company's stated purpose is: “Oppsett av nybygg, tilbygg, restaurering.”. The most recent filed accounts, for the 2025 financial year, show NOK 2.3m in revenue and NOK −62,000 in operating profit.

Key figures · 2025

Revenue
NOK 2.3m
▼ −64 %
Operating profit
NOK −62,000
▲ +79 %
Equity
NOK 22,000
▼ −75 %

Financial health · 2025

Liquidity
1.07
Satisfactory
Current assets ÷ current liabilities
Profitability
-15.6%
Not satisfactory
Return on total assets
Solidity
6.8%
Weak
Equity as a share of total capital

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

Who owns BRØDRENE UV AS?

BRØDRENE UV AS
NOK 2.3m rev. · NOK −62,000 profit

BRØDRENE UV AS has 2 registered shareholders:

All shareholders and roles →

Frequently asked questions about BRØDRENE UV AS

Who owns BRØDRENE UV AS?

Stig Erling Uv is the largest registered owner, with 50.0%.

What is the revenue of BRØDRENE UV AS?

BRØDRENE UV AS had revenue of NOK 2.3m in 2025.

Where is BRØDRENE UV AS based?

BRØDRENE UV AS has its business address in Oppaker.

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.