biztrac. BETA
COMPANY REGISTER PROFILE
921229143 ORG. NO. 2025 ACCOUNTS 8 SECTIONS
Active UPDATED 03.10.2026
Activities of specialist physicians, other than psychiatrists

NORDKIRURGI AS

Org. no. 921229143 Limited company (AS) Bærum Incorporated 2018 Active
Ownership graph ↗
Revenue 2025 NOK 1.0m
Operating profit NOK 152,000
Equity NOK 647,000
Incorporated 2018
Share capital NOK 30,000

Signals

1 flags
  • Nylig endring 2026-10-01 Adresseendring registrert 2026-10-01.

NORDKIRURGI AS is registered as a limited company in Bærum, Akershus with organisation number 921229143. The business is classified under activities of specialist physicians, other than psychiatrists (NACE 86.221). The company was incorporated in 2018. Registered share capital is NOK 30,000, divided into 30000 shares. The company's stated purpose is: “Medisinsk og kirurgisk service.”. The most recent filed accounts, for the 2025 financial year, show NOK 1.0m in revenue and NOK 152,000 in operating profit.

Key figures · 2025

Revenue
NOK 1.0m
▼ −30 %
Operating profit
NOK 152,000
▲ +660 %
Equity
NOK 647,000
▲ +1 %
Est. value
NOK 949,000

Financial health · 2025

Liquidity
5.70
Very good
Current assets ÷ current liabilities
Profitability
12.9%
Good
Return on total assets
Solidity
54.4%
Very good
Equity as a share of total capital

Who owns NORDKIRURGI AS?

NORDKIRURGI AS
NOK 1.0m rev. · NOK 152,000 profit

NORDKIRURGI AS has 1 registered shareholder:

All shareholders and roles →

Which companies does NORDKIRURGI AS own?

NORDKIRURGI AS holds stakes in 2 companies:

See the full ownership structure →

Frequently asked questions about NORDKIRURGI AS

Who owns NORDKIRURGI AS?

NORDSURG AS is the largest registered owner, with 100.0%.

What is the revenue of NORDKIRURGI AS?

NORDKIRURGI AS had revenue of NOK 1.0m in 2025.

Where is NORDKIRURGI AS based?

NORDKIRURGI AS has its business address in Eiksmarka.

Source: Biztrac.no · Data from the Brønnøysund Register Centre and the Norwegian Tax Administration · Last updated 03.10.2026.

Report a problem

Found a technical fault, or something wrong in the data? Tell us what happened.