BIZTRAC BETA
Joinery installation

SOLSKJERMING I BERGEN AS

Org. no. 929685377 Limited company (AS) Bergen Incorporated 2022 Active
Ownership graph ↗
Revenue 2025 NOK 852,000
Operating profit NOK 31,000
Equity NOK 129,000
Incorporated 2022
Share capital NOK 30,000

SOLSKJERMING I BERGEN AS is registered as a limited company in Bergen, Vestland with organisation number 929685377. The business is classified under joinery installation (NACE 43.320). The company was incorporated in 2022. Registered share capital is NOK 30,000, divided into 30000 shares. The company's stated purpose is: “Tilby produkter og tjenester innen solskjerming, herunder salg, montering, markedsføring og annen virksomhet som naturlig hører sammen med dette. Selskapet kan også eie aksjer i andre selskaper, delta i beslektet virksomhet, samt drive investering og rådgivning.”. The most recent filed accounts, for the 2025 financial year, show NOK 852,000 in revenue and NOK 31,000 in operating profit.

Key figures · 2025

Revenue
NOK 852,000
Operating profit
NOK 31,000
Equity
NOK 129,000
Est. value
NOK 168,000

Financial health · 2025

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

Who owns SOLSKJERMING I BERGEN AS?

CHRISTOFFER NÆSGAARD SÆTHRE
SOLSKJERMING I BERGEN AS
NOK 852,000 rev. · NOK 31,000 profit

SOLSKJERMING I BERGEN AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about SOLSKJERMING I BERGEN AS

Who owns SOLSKJERMING I BERGEN AS?

CHRISTOFFER NÆSGAARD SÆTHRE is the largest registered owner, with 100.0%.

What is the revenue of SOLSKJERMING I BERGEN AS?

SOLSKJERMING I BERGEN AS had revenue of NOK 852,000 in 2025.

Where is SOLSKJERMING I BERGEN AS based?

SOLSKJERMING I BERGEN AS has its business address in Rå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.