BIZTRAC BETA
Computer programming activities

MEDISINDAGBOKA AS

Org. no. 931612808 Limited company (AS) Tromsø Incorporated 2023 Active
Ownership graph ↗
Revenue 2024 NOK 579,000
Operating profit NOK 31,000
Equity NOK 90,000
Incorporated 2023
Share capital NOK 30,000

MEDISINDAGBOKA AS is registered as a limited company in Tromsø, Troms with organisation number 931612808. The business is classified under computer programming activities (NACE 62.100). The company was incorporated in 2023. Registered share capital is NOK 30,000, divided into 3000 shares. The company's stated purpose is: “Øke riktig bruk av legemidler og kunnskap om legemidler i samfunnet gjennom å tilby digitale løsninger og annet som naturlig faller sammen med dette.”. The most recent filed accounts, for the 2024 financial year, show NOK 579,000 in revenue and NOK 31,000 in operating profit.

Key figures · 2024

Revenue
NOK 579,000
Operating profit
NOK 31,000
Equity
NOK 90,000
Est. value
NOK 241,000

Financial health · 2024

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

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

Who owns MEDISINDAGBOKA AS?

RASMUS PEDERSEN
MEDISINDAGBOKA AS
NOK 579,000 rev. · NOK 31,000 profit

MEDISINDAGBOKA AS has 3 registered shareholders:

All shareholders and roles →

Frequently asked questions about MEDISINDAGBOKA AS

Who owns MEDISINDAGBOKA AS?

RASMUS PEDERSEN is the largest registered owner, with 33.3%.

What is the revenue of MEDISINDAGBOKA AS?

MEDISINDAGBOKA AS had revenue of NOK 579,000 in 2024.

Who is the general manager of MEDISINDAGBOKA AS?

Magnus Andersland Antonsen is registered as general manager of MEDISINDAGBOKA AS.

Where is MEDISINDAGBOKA AS based?

MEDISINDAGBOKA AS has its business address in Tomasjord.

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.