BIZTRAC BETA
Sports and recreation education

SPIRE ERNÆRING AS

Org. no. 914274001 Limited company (AS) Trondheim Incorporated 2014 Active
Ownership graph ↗
Revenue 2024 NOK 13,000
Operating profit NOK 155
Equity NOK 61,000
Incorporated 2014
Share capital NOK 30,000

SPIRE ERNÆRING AS is registered as a limited company in Trondheim, Trøndelag with organisation number 914274001. The business is classified under sports and recreation education (NACE 85.510). The company was incorporated in 2014. Registered share capital is NOK 30,000, divided into 100 shares. The company's stated purpose is: “Veiledning innen ernæring, trening og helse, kjøp og salg av aksjer, eller på annen måte gjøre seg interessert i andre foretagender.”. The most recent filed accounts, for the 2024 financial year, show NOK 13,000 in revenue and NOK 155 in operating profit.

Key figures · 2024

Revenue
NOK 13,000
Operating profit
NOK 155
Equity
NOK 61,000
Est. value
NOK 32,000

Financial health · 2024

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

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

Who owns SPIRE ERNÆRING AS?

INGRID GRANEGGEN BJØRKLIMARK
SPIRE ERNÆRING AS
NOK 13,000 rev. · NOK 155 profit

SPIRE ERNÆRING AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about SPIRE ERNÆRING AS

Who owns SPIRE ERNÆRING AS?

INGRID GRANEGGEN BJØRKLIMARK is the largest registered owner, with 100.0%.

What is the revenue of SPIRE ERNÆRING AS?

SPIRE ERNÆRING AS had revenue of NOK 13,000 in 2024.

Who is the general manager of SPIRE ERNÆRING AS?

Ingrid Graneggen Bjørklimark is registered as general manager of SPIRE ERNÆRING AS.

Where is SPIRE ERNÆRING AS based?

SPIRE ERNÆRING AS has its business address in Klæbu.

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.