BIZTRAC BETA
Sports and recreation education

EQUINE ANATOMY INSIGHT AS

Org. no. 925898015 Limited company (AS) Drammen Incorporated 2020 Active
Ownership graph ↗
Revenue 2025 NOK 116,000
Operating profit NOK 24,000
Equity NOK 51,000
Incorporated 2020
Share capital NOK 30,000

EQUINE ANATOMY INSIGHT AS is registered as a limited company in Drammen, Buskerud with organisation number 925898015. The business is classified under sports and recreation education (NACE 85.510). The company was incorporated in 2020. Registered share capital is NOK 30,000, divided into 100 shares. The company's stated purpose is: “Online undervisning.”. The most recent filed accounts, for the 2025 financial year, show NOK 116,000 in revenue and NOK 24,000 in operating profit.

Key figures · 2025

Revenue
NOK 116,000
Operating profit
NOK 24,000
Equity
NOK 51,000
Est. value
NOK 126,000

Financial health · 2025

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

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

Who owns EQUINE ANATOMY INSIGHT AS?

STINE ELMELUND LARSEN STRAUME
EQUINE ANATOMY INSIGHT AS
NOK 116,000 rev. · NOK 24,000 profit

EQUINE ANATOMY INSIGHT AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about EQUINE ANATOMY INSIGHT AS

Who owns EQUINE ANATOMY INSIGHT AS?

STINE ELMELUND LARSEN STRAUME is the largest registered owner, with 100.0%.

What is the revenue of EQUINE ANATOMY INSIGHT AS?

EQUINE ANATOMY INSIGHT AS had revenue of NOK 116,000 in 2025.

Who is the general manager of EQUINE ANATOMY INSIGHT AS?

Stine Elmelund Larsen Straume is registered as general manager of EQUINE ANATOMY INSIGHT AS.

Where is EQUINE ANATOMY INSIGHT AS based?

EQUINE ANATOMY INSIGHT AS has its business address in Drammen.

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.