BIZTRAC BETA
Computer consultancy and computer facilities management activities

AMUNDSEN BOOK AS

Org. no. 915738958 Limited company (AS) Gloppen Incorporated 2015 Active
Ownership graph ↗
Revenue 2025 NOK 942,000
Operating profit NOK −117,000
Equity NOK −23,000
Incorporated 2015
Share capital NOK 30,000

Signals

2 flags
  • Negativ egenkapital 2025 Bokført egenkapital er negativ (−23k kr).
  • Driftsunderskudd 2025 Siste driftsresultat er negativt (−117k kr).

AMUNDSEN BOOK AS is registered as a limited company in Gloppen, Vestland with organisation number 915738958. The business is classified under computer consultancy and computer facilities management activities (NACE 62.200). The company was incorporated in 2015. Registered share capital is NOK 30,000, divided into 100 shares. The company's stated purpose is: “Konsulent og rådgivning. Grafisk design og markedsføring.”. The most recent filed accounts, for the 2025 financial year, show NOK 942,000 in revenue and NOK −117,000 in operating profit.

Key figures · 2025

Revenue
NOK 942,000
Operating profit
NOK −117,000
Equity
NOK −23,000

Financial health · 2025

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

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

Who owns AMUNDSEN BOOK AS?

AMUNDSEN BOOK HOLDING AS
AMUNDSEN BOOK AS
NOK 942,000 rev. · NOK −117,000 profit

AMUNDSEN BOOK AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about AMUNDSEN BOOK AS

Who owns AMUNDSEN BOOK AS?

AMUNDSEN BOOK HOLDING AS is the largest registered owner, with 100.0%.

What is the revenue of AMUNDSEN BOOK AS?

AMUNDSEN BOOK AS had revenue of NOK 942,000 in 2025.

Where is AMUNDSEN BOOK AS based?

AMUNDSEN BOOK AS has its business address in Sandane.

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.