BIZTRAC BETA
COMPANY REGISTER PROFILE
943523959 ORG. NO. 2025 ACCOUNTS 7 SECTIONS
Active UPDATED 02.09.2026
Non-specialised retail sale of predominately food, beverages or tobacco

H SVED AS

Org. no. 943523959 Limited company (AS) Flatanger Incorporated 1986 Active
Ownership graph ↗
Revenue 2025 NOK 1.8m
Operating profit NOK 12,000
Equity NOK 696,000
Incorporated 1986
Share capital NOK 651,000

H SVED AS is registered as a limited company in Flatanger, Trøndelag with organisation number 943523959. The business is classified under non-specialised retail sale of predominately food, beverages or tobacco (NACE 47.110). The company was incorporated in 1986. Registered share capital is NOK 651,000. The company's stated purpose is: “Å drive med dagligvarehandel, samt annen virksomhet som naturlig hører sammen med dette , herunder å delta i andre selskap med lignende virksomhet, og kjøp og salg av aksjer eller på annen måte gjøre seg interessert i andre foretak.”. The most recent filed accounts, for the 2025 financial year, show NOK 1.8m in revenue and NOK 12,000 in operating profit.

Key figures · 2025

Revenue
NOK 1.8m
▼ −10 %
Operating profit
NOK 12,000
▲ +346 %
Equity
NOK 696,000
▲ +3 %
Est. value
NOK 417,000

Financial health · 2025

Liquidity
1.55
Good
Current assets ÷ current liabilities
Profitability
1.8%
Weak
Return on total assets
Solidity
53.2%
Very good
Equity as a share of total capital

Who owns H SVED AS?

H SVED AS has 4 registered shareholders:

All shareholders and roles →

Frequently asked questions about H SVED AS

Who owns H SVED AS?

TOR ENDRE SVED is the largest registered owner, with 70.8%.

What is the revenue of H SVED AS?

H SVED AS had revenue of NOK 1.8m in 2025.

Who is the general manager of H SVED AS?

Lars Johannes Sved is registered as general manager of H SVED AS.

Where is H SVED AS based?

H SVED AS has its business address in Oppland.

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

Report a problem

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