biztrac. BETA
COMPANY REGISTER PROFILE
925160180 ORG. NO. 2025 ACCOUNTS 8 SECTIONS
Active UPDATED 03.10.2026
Rental and operating of own or leased real estate

SORGENFRIGATEN 32 AS

Org. no. 925160180 Limited company (AS) Oslo Incorporated 2020 Active
Ownership graph ↗
Revenue 2025 NOK 1.5m
Operating profit NOK 953,000
Equity NOK 2.7m
Incorporated 2020
Share capital NOK 30,000

SORGENFRIGATEN 32 AS is registered as a limited company in Oslo, Oslo with organisation number 925160180. The business is classified under rental and operating of own or leased real estate (NACE 68.200). The company was incorporated in 2020. Registered share capital is NOK 30,000, divided into 30000 shares. The company's stated purpose is: “Drift og eie av fast eiendom, finansiering, handel, tjenesteyting og alt hva hermed står i forbindelse.”. The most recent filed accounts, for the 2025 financial year, show NOK 1.5m in revenue and NOK 953,000 in operating profit.

Key figures · 2025

Revenue
NOK 1.5m
▲ +3 %
Operating profit
NOK 953,000
▲ +47 %
Equity
NOK 2.7m
▲ +7 %
Est. value
NOK 4.0m

Financial health · 2025

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

Who owns SORGENFRIGATEN 32 AS?

SORGENFRIGATEN 32 AS
NOK 1.5m rev. · NOK 953,000 profit

SORGENFRIGATEN 32 AS has 2 registered shareholders:

All shareholders and roles →

Frequently asked questions about SORGENFRIGATEN 32 AS

Who owns SORGENFRIGATEN 32 AS?

AS VESLEMØY is the largest registered owner, with 50.0%.

What is the revenue of SORGENFRIGATEN 32 AS?

SORGENFRIGATEN 32 AS had revenue of NOK 1.5m in 2025.

Who is the general manager of SORGENFRIGATEN 32 AS?

Ida Kristine Wohrm is registered as general manager of SORGENFRIGATEN 32 AS.

Where is SORGENFRIGATEN 32 AS based?

SORGENFRIGATEN 32 AS has its business address in Oslo.

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.