BIZTRAC BETA
Business and other management consultancy activities

COACHING & KARRIEREKRAFT AS

Org. no. 933111660 Limited company (AS) Bergen Incorporated 2024 Active
Ownership graph ↗
Revenue 2024 NOK 1.1m
Operating profit NOK 96,000
Equity NOK 105,000
Incorporated 2024
Share capital NOK 30,000

COACHING & KARRIEREKRAFT AS is registered as a limited company in Bergen, Vestland with organisation number 933111660. The business is classified under business and other management consultancy activities (NACE 70.200). The company was incorporated in 2024. Registered share capital is NOK 30,000, divided into 300 shares. The company's stated purpose is: “Salg av tjenester innen Coaching, lederutvikling og mentoring.”. The most recent filed accounts, for the 2024 financial year, show NOK 1.1m in revenue and NOK 96,000 in operating profit.

Key figures · 2024

Revenue
NOK 1.1m
Operating profit
NOK 96,000
Equity
NOK 105,000
Est. value
NOK 531,000

Financial health · 2024

Liquidity
1.23
Satisfactory
Current assets ÷ current liabilities
Profitability
Not available
Return on total assets
Solidity
18.7%
Good
Equity as a share of total capital

Who owns COACHING & KARRIEREKRAFT AS?

VIVI LOFTAAS OSBERG
COACHING & KARRIEREKRAFT AS
NOK 1.1m rev. · NOK 96,000 profit

COACHING & KARRIEREKRAFT AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about COACHING & KARRIEREKRAFT AS

Who owns COACHING & KARRIEREKRAFT AS?

VIVI LOFTAAS OSBERG is the largest registered owner, with 100.0%.

What is the revenue of COACHING & KARRIEREKRAFT AS?

COACHING & KARRIEREKRAFT AS had revenue of NOK 1.1m in 2024.

Who is the general manager of COACHING & KARRIEREKRAFT AS?

Vivi Loftaas Osberg is registered as general manager of COACHING & KARRIEREKRAFT AS.

Where is COACHING & KARRIEREKRAFT AS based?

COACHING & KARRIEREKRAFT AS has its business address in Fyllingsdalen.

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.