biztrac. BETA
COMPANY REGISTER PROFILE
826419202 ORG. NO. 2025 ACCOUNTS 9 SECTIONS
Active UPDATED 03.10.2026
Buying and selling of own real estate

SAMUELSEN EIENDOMSINVEST AS

Org. no. 826419202 Limited company (AS) Tvedestrand Incorporated 2021 Active
Ownership graph ↗
Operating profit NOK −4,000
Equity NOK −605,000
Incorporated 2021
Share capital NOK 30,000

Signals

2 flags
  • Negativ egenkapital 2025 Bokført egenkapital er negativ (−605k kr).
  • Driftsunderskudd 2025 Siste driftsresultat er negativt (−4k kr).

SAMUELSEN EIENDOMSINVEST AS is registered as a limited company in Tvedestrand, Agder with organisation number 826419202. 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 30,000, divided into 3000 shares. The company's stated purpose is: “Kjøp. salg og utleie av eiendom.”.

Former names: NFH 210128 AS

Key figures · 2025

Operating profit
NOK −4,000
▼ −0 %
Equity
NOK −605,000
▼ −31 %

Financial health · 2025

Liquidity
–
Not available
Current assets ÷ current liabilities
Profitability
–
Not available
Return on total assets
Solidity
-16444.3%
Weak
Equity as a share of total capital

Solidity capped at Weak because equity is below NOK 100,000.

Who owns SAMUELSEN EIENDOMSINVEST AS?

SAMUELSEN EIENDOMSINVEST AS
· NOK −4,000 profit

SAMUELSEN EIENDOMSINVEST AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about SAMUELSEN EIENDOMSINVEST AS

Who owns SAMUELSEN EIENDOMSINVEST AS?

SEBASTIAN SAMUELSEN HOLDING AS is the largest registered owner, with 100.0%.

Who is the general manager of SAMUELSEN EIENDOMSINVEST AS?

Sebastian Samuel Samuelsen is registered as general manager of SAMUELSEN EIENDOMSINVEST AS.

Where is SAMUELSEN EIENDOMSINVEST AS based?

SAMUELSEN EIENDOMSINVEST AS has its business address in Tvedestrand.

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.