BIZTRAC BETA
Rental and operating of own or leased real estate

SOGSTIVEIEN 2 AS

Org. no. 817959482 Limited company (AS) Frogn Incorporated 2016 Active
Ownership graph ↗
Revenue 2025 NOK 400,000
Operating profit NOK 65,000
Equity NOK 368,000
Incorporated 2016
Share capital NOK 30,000

SOGSTIVEIEN 2 AS is registered as a limited company in Frogn, Akershus with organisation number 817959482. The business is classified under rental and operating of own or leased real estate (NACE 68.200). The company was incorporated in 2016. Registered share capital is NOK 30,000, divided into 300 shares. The company's stated purpose is: “Eie og utvikle eiendom og annet som naturlig faller sammen med dette, herunder å delta i andre selskaper med lignende virksomhet, kjøp og salg av aksjer, eller på annen måte gjøre seg interessert i andre foretagender.”. The most recent filed accounts, for the 2025 financial year, show NOK 400,000 in revenue and NOK 65,000 in operating profit.

Key figures · 2025

Revenue
NOK 400,000
Operating profit
NOK 65,000
Equity
NOK 368,000
Est. value
NOK 433,000

Financial health · 2025

Liquidity
0.58
Weak
Current assets ÷ current liabilities
Profitability
Not available
Return on total assets
Solidity
81.2%
Very good
Equity as a share of total capital

Who owns SOGSTIVEIEN 2 AS?

FOLLO EIENDOM AS
SOGSTIVEIEN 2 AS
NOK 400,000 rev. · NOK 65,000 profit

SOGSTIVEIEN 2 AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about SOGSTIVEIEN 2 AS

Who owns SOGSTIVEIEN 2 AS?

FOLLO EIENDOM AS is the largest registered owner, with 100.0%.

What is the revenue of SOGSTIVEIEN 2 AS?

SOGSTIVEIEN 2 AS had revenue of NOK 400,000 in 2025.

Who is the general manager of SOGSTIVEIEN 2 AS?

Mikal Rohde is registered as general manager of SOGSTIVEIEN 2 AS.

Where is SOGSTIVEIEN 2 AS based?

SOGSTIVEIEN 2 AS has its business address in Drøbak.

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.