BIZTRAC BETA
Business and other management consultancy activities

WELLINGTON AS

Org. no. 946668567 Limited company (AS) Evenes Incorporated 1988 Active
Ownership graph ↗
Revenue 2025 NOK 235,000
Operating profit NOK 94,000
Equity NOK 576,000
Incorporated 1988
Share capital NOK 100,000

WELLINGTON AS is registered as a limited company in Evenes, Nordland with organisation number 946668567. The business is classified under business and other management consultancy activities (NACE 70.200). The company was incorporated in 1988. Registered share capital is NOK 100,000, divided into 100 shares. The company's stated purpose is: “Bedriftsøkonomisk rådgivningsvirksomhet, særlig innen feltene finansiering, markedsføring, person- alutvikling og bedriftsutvikling, samt å drive virksomhet som står i naturlig forbindelse hermed og/eller delta i andre selskaper.”. The most recent filed accounts, for the 2025 financial year, show NOK 235,000 in revenue and NOK 94,000 in operating profit.

Key figures · 2025

Revenue
NOK 235,000
Operating profit
NOK 94,000
Equity
NOK 576,000
Est. value
NOK 696,000

Financial health · 2025

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

Who owns WELLINGTON AS?

FINN STEINAR HEIMLY
WELLINGTON AS
NOK 235,000 rev. · NOK 94,000 profit

WELLINGTON AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about WELLINGTON AS

Who owns WELLINGTON AS?

FINN STEINAR HEIMLY is the largest registered owner, with 100.0%.

What is the revenue of WELLINGTON AS?

WELLINGTON AS had revenue of NOK 235,000 in 2025.

Who is the general manager of WELLINGTON AS?

Finn Steinar Heimly is registered as general manager of WELLINGTON AS.

Where is WELLINGTON AS based?

WELLINGTON AS has its business address in Bogen I Ofoten.

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.