BIZTRAC BETA
All other professional, scientific and technical activities n.e.c.

EKSOTERM ØST AS

Org. no. 933556514 Limited company (AS) Bamble Incorporated 2024 Active
Ownership graph ↗
Revenue 2025 NOK 237,000
Operating profit NOK 19,000
Equity NOK 59,000
Incorporated 2024
Share capital NOK 30,000

EKSOTERM ØST AS is registered as a limited company in Bamble, Telemark with organisation number 933556514. The business is classified under all other professional, scientific and technical activities n.e.c. (NACE 74.990). The company was incorporated in 2024. Registered share capital is NOK 30,000, divided into 1000 shares. The company's stated purpose is: “Virksomhet innen forebyggende brannsikring og skadedyr samt enhver annen virksomhet som står i forbindelse med dette.”. The most recent filed accounts, for the 2025 financial year, show NOK 237,000 in revenue and NOK 19,000 in operating profit.

Key figures · 2025

Revenue
NOK 237,000
Operating profit
NOK 19,000
Equity
NOK 59,000
Est. value
NOK 132,000

Financial health · 2025

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

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

Who owns EKSOTERM ØST AS?

EKSOTERM AS
EKSOTERM ØST AS
NOK 237,000 rev. · NOK 19,000 profit

EKSOTERM ØST AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about EKSOTERM ØST AS

Who owns EKSOTERM ØST AS?

EKSOTERM AS is the largest registered owner, with 100.0%.

What is the revenue of EKSOTERM ØST AS?

EKSOTERM ØST AS had revenue of NOK 237,000 in 2025.

Who is the general manager of EKSOTERM ØST AS?

Vegard Holmberg Vigerust is registered as general manager of EKSOTERM ØST AS.

Where is EKSOTERM ØST AS based?

EKSOTERM ØST AS has its business address in Stathelle.

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.