biztrac. BETA
COMPANY REGISTER PROFILE
935366429 ORG. NO. 2025 ACCOUNTS 7 SECTIONS
Active UPDATED 03.10.2026
Construction of residential and non-residential buildings

STRANDBERG BYGG & VEDLIKEHOLD AS

Org. no. 935366429 Limited company (AS) Sandefjord Incorporated 2025 Active
Revenue 2025 NOK 647,000
Operating profit NOK 357,000
Equity NOK 308,000
Incorporated 2025
Share capital NOK 30,000

STRANDBERG BYGG & VEDLIKEHOLD AS is registered as a limited company in Sandefjord, Vestfold with organisation number 935366429. The business is classified under construction of residential and non-residential buildings (NACE 41.000). The company was incorporated in 2025. Registered share capital is NOK 30,000, divided into 100 shares. The company's stated purpose is: “Tjenester innen bygg og anlegg, trefelling og vaktmestertjenester.”. The most recent filed accounts, for the 2025 financial year, show NOK 647,000 in revenue and NOK 357,000 in operating profit.

Key figures · 2025

Revenue
NOK 647,000
Operating profit
NOK 357,000
Equity
NOK 308,000
Est. value
NOK 1.2m

Financial health · 2025

Liquidity
2.45
Very good
Current assets ÷ current liabilities
Profitability
–
Not available
Return on total assets
Solidity
68.2%
Very good
Equity as a share of total capital

Who owns STRANDBERG BYGG & VEDLIKEHOLD AS?

STRANDBERG BYGG & VEDLIKEHOLD AS
NOK 647,000 rev. · NOK 357,000 profit

STRANDBERG BYGG & VEDLIKEHOLD AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about STRANDBERG BYGG & VEDLIKEHOLD AS

Who owns STRANDBERG BYGG & VEDLIKEHOLD AS?

Andrè Strandberg is the largest registered owner, with 100.0%.

What is the revenue of STRANDBERG BYGG & VEDLIKEHOLD AS?

STRANDBERG BYGG & VEDLIKEHOLD AS had revenue of NOK 647,000 in 2025.

Where is STRANDBERG BYGG & VEDLIKEHOLD AS based?

STRANDBERG BYGG & VEDLIKEHOLD AS has its business address in Sandefjord.

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.