BIZTRAC BETA
Construction of residential and non-residential buildings

SKRENTEN BOLIG AS

Org. no. 930842850 Limited company (AS) Sandefjord Incorporated 2023 Active
Ownership graph ↗
Revenue 2025 NOK 346,000
Operating profit NOK 43,000
Equity NOK 127,000
Incorporated 2023
Share capital NOK 30,000

SKRENTEN BOLIG AS is registered as a limited company in Sandefjord, Vestfold with organisation number 930842850. 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: “Tømrertjenester og prosjektledelse.”. The most recent filed accounts, for the 2025 financial year, show NOK 346,000 in revenue and NOK 43,000 in operating profit.

Key figures · 2025

Revenue
NOK 346,000
Operating profit
NOK 43,000
Equity
NOK 127,000
Est. value
NOK 164,000

Financial health · 2025

Liquidity
10.91
Very good
Current assets ÷ current liabilities
Profitability
Not available
Return on total assets
Solidity
13.3%
Satisfactory
Equity as a share of total capital

Who owns SKRENTEN BOLIG AS?

ROBERT BLÅLID
SKRENTEN BOLIG AS
NOK 346,000 rev. · NOK 43,000 profit

SKRENTEN BOLIG AS has 1 registered shareholder:

All shareholders and roles →

Which companies does SKRENTEN BOLIG AS own?

SKRENTEN BOLIG AS holds a stake in 1 company:

See the full ownership structure →

Frequently asked questions about SKRENTEN BOLIG AS

Who owns SKRENTEN BOLIG AS?

ROBERT BLÅLID is the largest registered owner, with 100.0%.

What is the revenue of SKRENTEN BOLIG AS?

SKRENTEN BOLIG AS had revenue of NOK 346,000 in 2025.

Who is the general manager of SKRENTEN BOLIG AS?

Robert Blålid is registered as general manager of SKRENTEN BOLIG AS.

Where is SKRENTEN BOLIG AS based?

SKRENTEN BOLIG 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 15.06.2026.

Report a problem

Found a technical fault, or something wrong in the data? Tell us what happened.