BIZTRAC BETA
General medical practice activities

ROBRYGGA LEGEKONTOR AS

Org. no. 917449252 Limited company (AS) Namsos Incorporated 2016 Active
Ownership graph ↗
Revenue 2025 NOK 4.6m
Operating profit NOK 129,000
Equity NOK 270,000
Incorporated 2016
Share capital NOK 40,000

ROBRYGGA LEGEKONTOR AS is registered as a limited company in Namsos, Trøndelag with organisation number 917449252. The business is classified under general medical practice activities (NACE 86.210). The company was incorporated in 2016. Registered share capital is NOK 40,000, divided into 40 shares. The company's stated purpose is: “Å drive kontorfellesskap i tilknytning til helsetjenester og andre tjenester i tilknytning til dette samt virksomhet som står i naturlig forbindelse med dette.”. The most recent filed accounts, for the 2025 financial year, show NOK 4.6m in revenue and NOK 129,000 in operating profit.

Key figures · 2025

Revenue
NOK 4.6m
Operating profit
NOK 129,000
Equity
NOK 270,000
Est. value
NOK 772,000

Financial health · 2025

Liquidity
1.12
Satisfactory
Current assets ÷ current liabilities
Profitability
Not available
Return on total assets
Solidity
39.1%
Good
Equity as a share of total capital

Who owns ROBRYGGA LEGEKONTOR AS?

JON FRODE TRANAAS
ROBRYGGA LEGEKONTOR AS
NOK 4.6m rev. · NOK 129,000 profit

ROBRYGGA LEGEKONTOR AS has 4 registered shareholders:

All shareholders and roles →

Frequently asked questions about ROBRYGGA LEGEKONTOR AS

Who owns ROBRYGGA LEGEKONTOR AS?

JON FRODE TRANAAS is the largest registered owner, with 25.0%.

What is the revenue of ROBRYGGA LEGEKONTOR AS?

ROBRYGGA LEGEKONTOR AS had revenue of NOK 4.6m in 2025.

Who is the general manager of ROBRYGGA LEGEKONTOR AS?

Jan Laugen is registered as general manager of ROBRYGGA LEGEKONTOR AS.

Where is ROBRYGGA LEGEKONTOR AS based?

ROBRYGGA LEGEKONTOR AS has its business address in Namsos.

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.