BIZTRAC BETA
Computer consultancy and computer facilities management activities

REMTEK AS

Org. no. 933483355 Limited company (AS) Kristiansand Incorporated 2024 Active
Ownership graph ↗
Revenue 2025 NOK 130,000
Operating profit NOK 97,000
Equity NOK 77,000
Incorporated 2024
Share capital NOK 30,000

REMTEK AS is registered as a limited company in Kristiansand, Agder with organisation number 933483355. The business is classified under computer consultancy and computer facilities management activities (NACE 62.200). The company was incorporated in 2024. Registered share capital is NOK 30,000, divided into 30000 shares. The company's stated purpose is: “Selge varer og tjenester innen IT - og annet som naturlig sammenfaller med dette - samt deltakelse i andre selskaper, investeringer og nærliggende virksomhet.”. The most recent filed accounts, for the 2025 financial year, show NOK 130,000 in revenue and NOK 97,000 in operating profit.

Key figures · 2025

Revenue
NOK 130,000
Operating profit
NOK 97,000
Equity
NOK 77,000
Est. value
NOK 359,000

Financial health · 2025

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

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

Who owns REMTEK AS?

EMIL BERNHARD ESPEGREN
REMTEK AS
NOK 130,000 rev. · NOK 97,000 profit

REMTEK AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about REMTEK AS

Who owns REMTEK AS?

EMIL BERNHARD ESPEGREN is the largest registered owner, with 100.0%.

What is the revenue of REMTEK AS?

REMTEK AS had revenue of NOK 130,000 in 2025.

Who is the general manager of REMTEK AS?

Emil Bernhard Espegren is registered as general manager of REMTEK AS.

Where is REMTEK AS based?

REMTEK AS has its business address in Kristiansand S.

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.