BIZTRAC BETA
Roofing activities

TEAM ERIKSEN DRIFT AS

Org. no. 836265912 Limited company (AS) Harstad Incorporated 2025 Active
Ownership graph ↗
Revenue 2025 NOK 0
Operating profit NOK 0
Equity NOK 34,000
Incorporated 2025
Employees 9
Share capital NOK 30,000

Signals

1 flags
  • Nystiftet selskap Selskapet ble stiftet 2025-09-29.

TEAM ERIKSEN DRIFT AS is registered as a limited company in Harstad, Troms with organisation number 836265912. The business is classified under roofing activities (NACE 43.410). The company was incorporated in 2025 and has 9 registered employees. Registered share capital is NOK 30,000, divided into 30000 shares. The company's stated purpose is: “Taktekking og annen virksomhet som naturlig faller inn under dette.”. The most recent filed accounts, for the 2025 financial year, show NOK 0 in revenue and NOK 0 in operating profit.

Key figures · 2025

Revenue
NOK 0
Operating profit
NOK 0
Equity
NOK 34,000
Est. value
NOK 34,000

Financial health · 2025

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

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

Who owns TEAM ERIKSEN DRIFT AS?

FIRKANTEN HOLDING AS
TEAM ERIKSEN DRIFT AS
NOK 0 rev. · NOK 0 profit

TEAM ERIKSEN DRIFT AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about TEAM ERIKSEN DRIFT AS

Who owns TEAM ERIKSEN DRIFT AS?

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

What is the revenue of TEAM ERIKSEN DRIFT AS?

TEAM ERIKSEN DRIFT AS had revenue of NOK 0 in 2025.

Who is the general manager of TEAM ERIKSEN DRIFT AS?

Harald Eriksen is registered as general manager of TEAM ERIKSEN DRIFT AS.

Where is TEAM ERIKSEN DRIFT AS based?

TEAM ERIKSEN DRIFT AS has its business address in Harstad.

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.