biztrac. BETA
COMPANY REGISTER PROFILE
917648107 ORG. NO. 2025 ACCOUNTS 8 SECTIONS
Active UPDATED 03.10.2026
Rental and operating of own or leased real estate

INSERT COINS AS

Org. no. 917648107 Limited company (AS) Porsgrunn Incorporated 2016 Active
Ownership graph ↗
Revenue 2025 NOK 0
Operating profit NOK −28,000
Equity NOK 8.9m
Incorporated 2016
Share capital NOK 250,000

Signals

1 flags
  • Driftsunderskudd 2025 Siste driftsresultat er negativt (−28k kr).

INSERT COINS AS is registered as a limited company in Porsgrunn, Telemark with organisation number 917648107. The business is classified under rental and operating of own or leased real estate (NACE 68.200). The company was incorporated in 2016. Registered share capital is NOK 250,000, divided into 2500 shares. The company's stated purpose is: “Investeringer i aksjer, verdipapirer og fast eiendom.”. The most recent filed accounts, for the 2025 financial year, show NOK 0 in revenue and NOK −28,000 in operating profit.

Key figures · 2025

Revenue
NOK 0
Operating profit
NOK −28,000
▼ −26 %
Equity
NOK 8.9m
▲ +233 %
Est. value
NOK 29.5m

Financial health · 2025

Liquidity
134.62
Very good
Current assets ÷ current liabilities
Profitability
108.8%
Very good
Return on total assets
Solidity
99.5%
Very good
Equity as a share of total capital

Who owns INSERT COINS AS?

INSERT COINS AS
NOK 0 rev. · NOK −28,000 profit

INSERT COINS AS has 1 registered shareholder:

All shareholders and roles →

Which companies does INSERT COINS AS own?

INSERT COINS AS holds a stake in 1 company:

See the full ownership structure →

Frequently asked questions about INSERT COINS AS

Who owns INSERT COINS AS?

Trygve Fredrik Tveit is the largest registered owner, with 100.0%.

What is the revenue of INSERT COINS AS?

INSERT COINS AS had revenue of NOK 0 in 2025.

Where is INSERT COINS AS based?

INSERT COINS AS has its business address in Porsgrunn.

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.