BIZTRAC BETA
Other technical consultancy

TAS LOBE INVEST AS

Org. no. 913941497 Limited company (AS) Kristiansand Incorporated 2014 Active
Ownership graph ↗
Revenue 2024 NOK 507,000
Operating profit NOK 60,000
Equity NOK 4.4m
Incorporated 2014
Share capital NOK 102,000

TAS LOBE INVEST AS is registered as a limited company in Kristiansand, Agder with organisation number 913941497. The business is classified under other technical consultancy (NACE 71.129). The company was incorporated in 2014. Registered share capital is NOK 102,000, divided into 10168379 shares. The company's stated purpose is: “Selskapet skal kunne utvikle kommunikasjonsutstyr, antenner eller alt som naturlig hører inn under denne utstyrskategorien. Selskapet skal også kunne delta i andres selskaper eller som aksjonær i disse.”. The most recent filed accounts, for the 2024 financial year, show NOK 507,000 in revenue and NOK 60,000 in operating profit.

Key figures · 2024

Revenue
NOK 507,000
Operating profit
NOK 60,000
Equity
NOK 4.4m
Est. value
NOK 2.5m

Financial health · 2024

Liquidity
3.32
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 TAS LOBE INVEST AS?

SVEIN OLAF OLSEN
TAS LOBE INVEST AS
NOK 507,000 rev. · NOK 60,000 profit

TAS LOBE INVEST AS has 9 registered shareholders:

All shareholders and roles →

Frequently asked questions about TAS LOBE INVEST AS

Who owns TAS LOBE INVEST AS?

SVEIN OLAF OLSEN is the largest registered owner, with 56.2%.

What is the revenue of TAS LOBE INVEST AS?

TAS LOBE INVEST AS had revenue of NOK 507,000 in 2024.

Who is the general manager of TAS LOBE INVEST AS?

Svein Olaf Olsen is registered as general manager of TAS LOBE INVEST AS.

Where is TAS LOBE INVEST AS based?

TAS LOBE INVEST 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.