biztrac. BETA
COMPANY REGISTER PROFILE
813297302 ORG. NO. 2025 ACCOUNTS 8 SECTIONS
Active UPDATED 03.10.2026
General medical practice activities

DR. LARS FURUSETH AS

Org. no. 813297302 Limited company (AS) Tønsberg Incorporated 2014 Active
Ownership graph ↗
Revenue 2025 NOK 2.5m
Operating profit NOK 157,000
Equity NOK 496,000
Incorporated 2014
Share capital NOK 30,000

DR. LARS FURUSETH AS is registered as a limited company in Tønsberg, Vestfold with organisation number 813297302. The business is classified under general medical practice activities (NACE 86.210). The company was incorporated in 2014. Registered share capital is NOK 30,000, divided into 30 shares. The company's stated purpose is: “Allmennlege og alt som faller naturlig inn under dette. Deltakelse i andre selskaper.”. The most recent filed accounts, for the 2025 financial year, show NOK 2.5m in revenue and NOK 157,000 in operating profit.

Key figures · 2025

Revenue
NOK 2.5m
▲ +0 %
Operating profit
NOK 157,000
▼ −65 %
Equity
NOK 496,000
▼ −12 %
Est. value
NOK 1.3m

Financial health · 2025

Liquidity
2.83
Very good
Current assets ÷ current liabilities
Profitability
19.5%
Very good
Return on total assets
Solidity
64.7%
Very good
Equity as a share of total capital

Who owns DR. LARS FURUSETH AS?

DR. LARS FURUSETH AS
NOK 2.5m rev. · NOK 157,000 profit

DR. LARS FURUSETH AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about DR. LARS FURUSETH AS

Who owns DR. LARS FURUSETH AS?

Lars Furuseth is the largest registered owner, with 100.0%.

What is the revenue of DR. LARS FURUSETH AS?

DR. LARS FURUSETH AS had revenue of NOK 2.5m in 2025.

Who is the general manager of DR. LARS FURUSETH AS?

Lars Furuseth is registered as general manager of DR. LARS FURUSETH AS.

Where is DR. LARS FURUSETH AS based?

DR. LARS FURUSETH AS has its business address in Tolvsrød.

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.