BIZTRAC BETA
COMPANY REGISTER PROFILE
922154902 ORG. NO. 2025 ACCOUNTS 7 SECTIONS
Active UPDATED 02.09.2026
Other technical consultancy

FOLLEVAAG OFFSHORE AS

Org. no. 922154902 Limited company (AS) Askøy Incorporated 2019 Active
Ownership graph ↗
Equity NOK 0
Incorporated 2019
Share capital NOK 30,000

FOLLEVAAG OFFSHORE AS is registered as a limited company in Askøy, Vestland with organisation number 922154902. The business is classified under other technical consultancy (NACE 71.129). The company was incorporated in 2019. Registered share capital is NOK 30,000, divided into 100 shares. The company's stated purpose is: “Teknisk konsulentvirksomhet, samt alt som hører naturlig til dette.”.

Key figures · 2025

Equity
NOK 0

Financial health · 2025

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

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

Who owns FOLLEVAAG OFFSHORE AS?

FOLLEVAAG OFFSHORE AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about FOLLEVAAG OFFSHORE AS

Who owns FOLLEVAAG OFFSHORE AS?

KIM-ARNE VEIVÅG FOLLEVAAG is the largest registered owner, with 100.0%.

Who is the general manager of FOLLEVAAG OFFSHORE AS?

Kim-Arne Veivåg Follevaag is registered as general manager of FOLLEVAAG OFFSHORE AS.

Where is FOLLEVAAG OFFSHORE AS based?

FOLLEVAAG OFFSHORE AS has its business address in Hauglandshella.

Property

Business address Davangervegen 95, 5310 Hauglandshella
Cadastral unit 4627-21/90/0/0
Building Enebolig · 1 unit

The address this company is registered at, from the company register and matched against the cadastre. It does not say who owns the property — a company may be a tenant, and the address is often its accountant's. Source: Brønnøysundregistrene and © Kartverket.

Source: Biztrac.no · Data from the Brønnøysund Register Centre and the Norwegian Tax Administration · Last updated 02.09.2026.

Report a problem

Found a technical fault, or something wrong in the data? Tell us what happened.