biztrac. BETA
COMPANY REGISTER PROFILE
928744078 ORG. NO. 2025 ACCOUNTS 9 SECTIONS
Active UPDATED 03.10.2026
Support services to forestry

STEA HOLDING AS

Org. no. 928744078 Limited company (AS) Vegårshei Incorporated 2022 Active
Ownership graph ↗
Operating profit NOK −6,000
Equity NOK 13,000
Incorporated 2022
Share capital NOK 30,000

Signals

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

STEA HOLDING AS is registered as a limited company in Vegårshei, Agder with organisation number 928744078. The business is classified under support services to forestry (NACE 02.400). The company was incorporated in 2022. Registered share capital is NOK 30,000, divided into 200000 shares. The company's stated purpose is: “Tradisjonell tømmerdrift, avskoging av tomteområder, veikanthogst mm. Selskapet kan eie aksjer/andeler i andre selskaper.”.

Former names: 16.1 EIENDOM AS, SØRLANDET AVSKOGING AS

Key figures · 2025

Operating profit
NOK −6,000
▼ −3 %
Equity
NOK 13,000
▼ −93 %
Est. value
NOK 12,000

Financial health · 2025

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

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

Who owns STEA HOLDING AS?

STEA HOLDING AS
· NOK −6,000 profit

STEA HOLDING AS has 1 registered shareholder:

All shareholders and roles →

Which companies does STEA HOLDING AS own?

STEA HOLDING AS holds a stake in 1 company:

See the full ownership structure →

Frequently asked questions about STEA HOLDING AS

Who owns STEA HOLDING AS?

Knut Erlend Mevatne is the largest registered owner, with 100.0%.

Who is the general manager of STEA HOLDING AS?

Knut Erlend Mevatne is registered as general manager of STEA HOLDING AS.

Where is STEA HOLDING AS based?

STEA HOLDING AS has its business address in Vegårshei.

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.