BIZTRAC BETA
Construction of residential and non-residential buildings

ERIK VALLE & SØNN AS

Org. no. 931734334 Limited company (AS) Vestby Incorporated 2023 Active
Ownership graph ↗
Revenue 2025 NOK 3.3m
Operating profit NOK −89,000
Equity NOK 45,000
Incorporated 2023
Share capital NOK 30,000

Signals

1 flags
  • Driftsunderskudd 2025 Siste driftsresultat er negativt (−89k kr).

ERIK VALLE & SØNN AS is registered as a limited company in Vestby, Akershus with organisation number 931734334. The business is classified under construction of residential and non-residential buildings (NACE 41.000). The company was incorporated in 2023. Registered share capital is NOK 30,000, divided into 50 shares. The company's stated purpose is: “Handel og byggevirksomhet, herunder kjøp, salg, oppføring og vedlikehold av fast eiendom, samt deltagelse i andre selskaper med beslektet virksomhet.”. The most recent filed accounts, for the 2025 financial year, show NOK 3.3m in revenue and NOK −89,000 in operating profit.

Key figures · 2025

Revenue
NOK 3.3m
Operating profit
NOK −89,000
Equity
NOK 45,000
Est. value
NOK 1.2m

Financial health · 2025

Liquidity
0.77
Weak
Current assets ÷ current liabilities
Profitability
Not available
Return on total assets
Solidity
5.1%
Weak
Equity as a share of total capital

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

Who owns ERIK VALLE & SØNN AS?

ERIK VALLE
ERIK VALLE & SØNN AS
NOK 3.3m rev. · NOK −89,000 profit

ERIK VALLE & SØNN AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about ERIK VALLE & SØNN AS

Who owns ERIK VALLE & SØNN AS?

ERIK VALLE is the largest registered owner, with 100.0%.

What is the revenue of ERIK VALLE & SØNN AS?

ERIK VALLE & SØNN AS had revenue of NOK 3.3m in 2025.

Where is ERIK VALLE & SØNN AS based?

ERIK VALLE & SØNN AS has its business address in Son.

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.