BIZTRAC BETA
Construction of residential and non-residential buildings

SON BYGG OG VEDLIKEHOLD AS

Org. no. 931914464 Limited company (AS) Vestby Incorporated 2023 Active
Ownership graph ↗
Revenue 2025 NOK 490,000
Operating profit NOK 9,000
Equity NOK 55,000
Incorporated 2023
Share capital NOK 30,000

SON BYGG OG VEDLIKEHOLD AS is registered as a limited company in Vestby, Akershus with organisation number 931914464. 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 100 shares. The company's stated purpose is: “Byggetjenester.”. The most recent filed accounts, for the 2025 financial year, show NOK 490,000 in revenue and NOK 9,000 in operating profit.

Key figures · 2025

Revenue
NOK 490,000
Operating profit
NOK 9,000
Equity
NOK 55,000
Est. value
NOK 60,000

Financial health · 2025

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

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

Who owns SON BYGG OG VEDLIKEHOLD AS?

KRISTOFFER HANSEN
SON BYGG OG VEDLIKEHOLD AS
NOK 490,000 rev. · NOK 9,000 profit

SON BYGG OG VEDLIKEHOLD AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about SON BYGG OG VEDLIKEHOLD AS

Who owns SON BYGG OG VEDLIKEHOLD AS?

KRISTOFFER HANSEN is the largest registered owner, with 100.0%.

What is the revenue of SON BYGG OG VEDLIKEHOLD AS?

SON BYGG OG VEDLIKEHOLD AS had revenue of NOK 490,000 in 2025.

Who is the general manager of SON BYGG OG VEDLIKEHOLD AS?

Kristoffer Hansen is registered as general manager of SON BYGG OG VEDLIKEHOLD AS.

Where is SON BYGG OG VEDLIKEHOLD AS based?

SON BYGG OG VEDLIKEHOLD 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.