BIZTRAC BETA
COMPANY REGISTER PROFILE
827018422 ORG. NO. 2025 ACCOUNTS 7 SECTIONS
Active UPDATED 02.09.2026
Buying and selling of own real estate

SIMONSEN-INVEST AS

Org. no. 827018422 Limited company (AS) Skien Incorporated 2021 Active
Ownership graph ↗
Operating profit NOK −4,000
Equity NOK 416,000
Incorporated 2021
Share capital NOK 33,000

Signals

1 flags
  • Driftsunderskudd 2025 Siste driftsresultat er negativt (−4k kr).

SIMONSEN-INVEST AS is registered as a limited company in Skien, Telemark with organisation number 827018422. The business is classified under buying and selling of own real estate (NACE 68.110). The company was incorporated in 2021. Registered share capital is NOK 33,000, divided into 30 shares. The company's stated purpose is: “Investering i aksjer og eiendom o.l. lukket for allmennheten.”.

Key figures · 2025

Operating profit
NOK −4,000
▲ +4 %
Equity
NOK 416,000
▼ −1 %
Est. value
NOK 380,000

Financial health · 2025

Liquidity
-69359.67
Not satisfactory
Current assets ÷ current liabilities
Profitability
Not available
Return on total assets
Solidity
100.0%
Very good
Equity as a share of total capital

Who owns SIMONSEN-INVEST AS?

SIMONSEN-INVEST AS
· NOK −4,000 profit

SIMONSEN-INVEST AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about SIMONSEN-INVEST AS

Who owns SIMONSEN-INVEST AS?

VEGARD SIMONSEN is the largest registered owner, with 100.0%.

Where is SIMONSEN-INVEST AS based?

SIMONSEN-INVEST AS has its business address in Skien.

Property

Business address Vestre Gulset 161, 3742 Skien
Cadastral unit 4003-2/13/0/0
Building Enebolig · 1 unit

The address this company is registered at, from the company register and matched against the cadastre. It does not say who owns the property — a company may be a tenant, and the address is often its accountant's. Source: Brønnøysundregistrene and © Kartverket.

Source: Biztrac.no · Data from the Brønnøysund Register Centre and the Norwegian Tax Administration · Last updated 02.09.2026.

Report a problem

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