BIZTRAC BETA
Other health services

GODTRENING AS

Org. no. 914317444 Limited company (AS) Øygarden Incorporated 2014 Active
Ownership graph ↗
Revenue 2024 NOK 256,000
Operating profit NOK 171,000
Equity NOK −110,000
Incorporated 2014
Share capital NOK 100,000

Signals

1 flags
  • Negativ egenkapital 2024 Bokført egenkapital er negativ (−110k kr).

GODTRENING AS is registered as a limited company in Øygarden, Vestland with organisation number 914317444. The business is classified under other health services (NACE 86.993). The company was incorporated in 2014. Registered share capital is NOK 100,000, divided into 333 shares. The company's stated purpose is: “Tilby konsulenttjenester innenfor helse, trening og ernæring.”. The most recent filed accounts, for the 2024 financial year, show NOK 256,000 in revenue and NOK 171,000 in operating profit.

Key figures · 2024

Revenue
NOK 256,000
Operating profit
NOK 171,000
Equity
NOK −110,000
Est. value
NOK 949,000

Financial health · 2025

Liquidity
1.21
Satisfactory
Current assets ÷ current liabilities
Profitability
Not available
Return on total assets
Solidity
-14.0%
Weak
Equity as a share of total capital

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

Who owns GODTRENING AS?

BREKKE HARUNG HOLDNING AS
GODTRENING AS
NOK 256,000 rev. · NOK 171,000 profit

GODTRENING AS has 1 registered shareholder:

All shareholders and roles →

Group structure

GODTRENING AS er morselskap for 2 datterselskaper:

Frequently asked questions about GODTRENING AS

Who owns GODTRENING AS?

BREKKE HARUNG HOLDNING AS is the largest registered owner, with 100.0%.

What is the revenue of GODTRENING AS?

GODTRENING AS had revenue of NOK 256,000 in 2024.

Who is the general manager of GODTRENING AS?

Guri Brekke is registered as general manager of GODTRENING AS.

Where is GODTRENING AS based?

GODTRENING AS has its business address in Brattholmen.

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.