BIZTRAC BETA
COMPANY REGISTER PROFILE
915318193 ORG. NO. 2025 ACCOUNTS 7 SECTIONS
Active UPDATED 02.09.2026
Construction of residential and non-residential buildings

NORSELOG AS

Org. no. 915318193 Limited company (AS) Ringsaker Incorporated 2015 Active
Ownership graph ↗
Revenue 2025 NOK 205,000
Operating profit NOK 167,000
Equity NOK 2.7m
Incorporated 2015
Share capital NOK 30,000

NORSELOG AS is registered as a limited company in Ringsaker, Innlandet with organisation number 915318193. The business is classified under construction of residential and non-residential buildings (NACE 41.000). The company was incorporated in 2015. Registered share capital is NOK 30,000, divided into 30 shares. The company's stated purpose is: “Investere i andre selskaper og hva derved står i sammenheng. I tillegg drive salg av materiell og øvrige tjenester knyttet til fast eiendom.”. The most recent filed accounts, for the 2025 financial year, show NOK 205,000 in revenue and NOK 167,000 in operating profit.

Key figures · 2025

Revenue
NOK 205,000
Operating profit
NOK 167,000
▲ +990 %
Equity
NOK 2.7m
▼ −4 %
Est. value
NOK 1.6m

Financial health · 2025

Liquidity
2.60
Very good
Current assets ÷ current liabilities
Profitability
6.1%
Satisfactory
Return on total assets
Solidity
98.3%
Very good
Equity as a share of total capital

Who owns NORSELOG AS?

NORSELOG AS
NOK 205,000 rev. · NOK 167,000 profit

NORSELOG AS has 1 registered shareholder:

All shareholders and roles →

Which companies does NORSELOG AS own?

NORSELOG AS holds stakes in 2 companies:

See the full ownership structure →

Frequently asked questions about NORSELOG AS

Who owns NORSELOG AS?

TERJE STRAND is the largest registered owner, with 100.0%.

What is the revenue of NORSELOG AS?

NORSELOG AS had revenue of NOK 205,000 in 2025.

Where is NORSELOG AS based?

NORSELOG AS has its business address in Gaupen.

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.