BIZTRAC BETA
COMPANY REGISTER PROFILE
926970135 ORG. NO. 2025 ACCOUNTS 7 SECTIONS
Active UPDATED 15.06.2026
Uoppgitt

SEIL INVEST AS

Org. no. 926970135 Limited company (AS) Porsgrunn Incorporated 2021 Active
Ownership graph ↗
Revenue 2025 NOK 38,000
Operating profit NOK 12,000
Equity NOK 52,000
Incorporated 2021
Share capital NOK 30,000

SEIL INVEST AS is registered as a limited company in Porsgrunn, Telemark with organisation number 926970135. The business is classified under uoppgitt (NACE 00.000). The company was incorporated in 2021. Registered share capital is NOK 30,000, divided into 30 shares. The company's stated purpose is: “Investering i andre selskaper.”. The most recent filed accounts, for the 2025 financial year, show NOK 38,000 in revenue and NOK 12,000 in operating profit.

Key figures · 2025

Revenue
NOK 38,000
Operating profit
NOK 12,000
Equity
NOK 52,000
Est. value
NOK 65,000

Financial health · 2025

Liquidity
1.49
Satisfactory
Current assets ÷ current liabilities
Profitability
Not available
Return on total assets
Solidity
48.3%
Weak
Equity as a share of total capital

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

Who owns SEIL INVEST AS?

KENNETH JOHANSEN
SEIL INVEST AS
NOK 38,000 rev. · NOK 12,000 profit

SEIL INVEST AS has 1 registered shareholder:

All shareholders and roles →

Which companies does SEIL INVEST AS own?

SEIL INVEST AS holds a stake in 1 company:

See the full ownership structure →

Frequently asked questions about SEIL INVEST AS

Who owns SEIL INVEST AS?

KENNETH JOHANSEN is the largest registered owner, with 100.0%.

What is the revenue of SEIL INVEST AS?

SEIL INVEST AS had revenue of NOK 38,000 in 2025.

Who is the general manager of SEIL INVEST AS?

Kenneth Johansen is registered as general manager of SEIL INVEST AS.

Where is SEIL INVEST AS based?

SEIL INVEST AS has its business address in Porsgrunn.

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.