BIZTRAC BETA
Construction of residential and non-residential buildings

UTVENDIG RENOVERING AS

Org. no. 930158747 Limited company (AS) Eidsvoll Incorporated 2022 Active
Ownership graph ↗
Revenue 2025 NOK 2.7m
Operating profit NOK 94,000
Equity NOK 178,000
Incorporated 2022
Employees 6
Share capital NOK 30,000

UTVENDIG RENOVERING AS is registered as a limited company in Eidsvoll, Akershus with organisation number 930158747. The business is classified under construction of residential and non-residential buildings (NACE 41.000). The company was incorporated in 2022 and has 6 registered employees. Registered share capital is NOK 30,000, divided into 100 shares. The company's stated purpose is: “Oppføring av bygninger, rehabiliteringsarbeid, maling og snekkerarbeid.”. The most recent filed accounts, for the 2025 financial year, show NOK 2.7m in revenue and NOK 94,000 in operating profit.

Key figures · 2025

Revenue
NOK 2.7m
Operating profit
NOK 94,000
Equity
NOK 178,000
Est. value
NOK 393,000

Financial health · 2025

Liquidity
1.72
Good
Current assets ÷ current liabilities
Profitability
Not available
Return on total assets
Solidity
46.2%
Very good
Equity as a share of total capital

Who owns UTVENDIG RENOVERING AS?

FORNYELSE GRUPPEN AS
UTVENDIG RENOVERING AS
NOK 2.7m rev. · NOK 94,000 profit

UTVENDIG RENOVERING AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about UTVENDIG RENOVERING AS

Who owns UTVENDIG RENOVERING AS?

FORNYELSE GRUPPEN AS is the largest registered owner, with 100.0%.

What is the revenue of UTVENDIG RENOVERING AS?

UTVENDIG RENOVERING AS had revenue of NOK 2.7m in 2025.

Who is the general manager of UTVENDIG RENOVERING AS?

Remigijus Kuodis is registered as general manager of UTVENDIG RENOVERING AS.

Where is UTVENDIG RENOVERING AS based?

UTVENDIG RENOVERING AS has its business address in Dal.

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.